How severe is CVE-2026-75956?

CVE-2026-75956 has a CVSS 4.0 base score of 8.7, rated high severity.

Is CVE-2026-75956 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (24th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-75956?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2026-75956 published?

CVE-2026-75956 was published on 2026-08-19 and last updated on 2026-08-21.

CVE-2026-75956

CVE-2026-75956 is a high-severity vulnerability with a CVSS 4.0 base score of 8.7. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-770.

Key facts

Severity: High (CVSS 4.0 base score 8.7)
EPSS exploit prediction: 0% (24th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-770
Published: 2026-08-19
Last modified: 2026-08-21

Description

Joomla Extension - cmsjunkie.com - DOS vector in pagination parameter handling in J-BusinessDirectory < 6.2.3 - Pagination values were not strictly typed. Array/non-numeric values (for example limitstart[]) could trigger PHP type errors in arithmetic, and limit was not validated before use in list queries.

Frequently asked questions

What is CVE-2026-75956?: Joomla Extension - cmsjunkie.com - DOS vector in pagination parameter handling in J-BusinessDirectory < 6.2.3 - Pagination values were not strictly typed. Array/non-numeric values (for example limitstart[]) could trigger PHP type errors in arithmetic, and limit was not validated before use in list queries.
How severe is CVE-2026-75956?: CVE-2026-75956 has a CVSS 4.0 base score of 8.7, rated high severity.
Is CVE-2026-75956 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (24th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-75956?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2026-75956 published?: CVE-2026-75956 was published on 2026-08-19 and last updated on 2026-08-21.

References

https://www.cmsjunkie.com/

Other CWE-770 (Allocation of Resources Without Limits or Throttling) vulnerabilities

CVE-2026-63299 — Critical (CVSS 9.9): An authorization bypass vulnerability in LXD allows an authenticated user to bypass project-level disk and volume…
CVE-2026-74878 — Critical (CVSS 9.8): openssl_encrypt versions before 1.4.0 use an in-memory rate limiter for TOTP brute-force protection that is not shared…
CVE-2026-31283 — Critical (CVSS 9.8): In Totara LMS v19.1.5 and before, the forgot password API does not implement rate limiting for the target email…
CVE-2020-37067 — Critical (CVSS 9.8): Filetto 1.0 FTP server contains a denial of service vulnerability in the FEAT command processing that allows attackers…
CVE-2021-47875 — Critical (CVSS 9.8): GeoGebra CAS Calculator 6.0.631.0 contains a denial of service vulnerability that allows attackers to crash the…
CVE-2025-11832 — Critical (CVSS 9.8): Allocation of Resources Without Limits or Throttling vulnerability in Azure Access Technology BLU-IC2, Azure Access…

Browse all CWE-770 (Allocation of Resources Without Limits or Throttling) vulnerabilities →