How severe is CVE-2023-23752?

CVE-2023-23752 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2023-23752?

Affected package information for CVE-2023-23752 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2023-23752?

No fixed version has been published for CVE-2023-23752 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2023-23752 actively exploited in the wild?

Yes. There are 39 known exploit references for CVE-2023-23752, including 1 documented proof-of-concept exploit on Exploit-DB and 23 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2023-23752?

CVE-2023-23752 has an EPSS (Exploit Prediction Scoring System) score of 94.5%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2023-23752 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2023-23752 (Joomla! Improper Access Control Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2024-01-08. CISA required all US federal civilian agencies to remediate this vulnerability by 2024-01-29. The required action was: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

Is there exploit tooling available for CVE-2023-23752?

A Nuclei detection template exists for CVE-2023-23752, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2023-23752 published, and has it been updated?

CVE-2023-23752 was published on February 16, 2023 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2024-01-08 — agencies required to remediate by 2024-01-29

CVE-2023-23752

MEDIUM

Also known asBIT-joomla-2023-23752

Published

Feb 16, 2023

Updated

Apr 10, 2026

Affected

0 pkgs

Patched

None yet

Exploits

39 known

EPSS Exploitation Probability

via FIRST.org ↗

94.5%probability of exploitation in next 30 days

Very High Risk100th percentile+0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

An issue was discovered in Joomla! 4.0.0 through 4.2.7. An improper access check allows unauthorized access to webservice endpoints.

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-51334webappsphp✓ Verified

Joomla! v4.2.8 - Unauthenticated information disclosure

by Alexandre ZANNI · Apr 8, 2023

Exploit-DB Source

Frequently Asked Questions

An issue was discovered in Joomla! 4.0.0 through 4.2.7. An improper access check allows unauthorized access to webservice endpoints.

O3 Security · Impact-Aware SCA

Is CVE-2023-23752 in your stack?

O3 detects CVE-2023-23752 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works