What is CVE-2023-23752?

CVE-2023-23752 is [20230201] - Core - Improper access check in webservice endpoints. The supplied enrichment data classifies it as Access Control mapped to CWE-284 Improper Access Control.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Yes: CISA KEV signal present. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

Is there a public exploit?

151 public PoC repositories reported; 1 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2023-23752 using CVSS 5.3, EPSS 100%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Treat as emergency remediation because CISA KEV status is present. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

CISA KEVmediumAccess Controlpublic exploit

CVE-2023-23752

CVE-2023-23752 — [20230201] - Core - Improper access check in webservice endpoints

Q: Is it in CISA KEV?

Yes. The supplied enrichment data lists CVE-2023-23752 in CISA KEV with required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

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

Published Feb 16, 2023Updated Jun 17, 2026Sources: NVD, Joomla! Project (CNA), CISA, FIRST EPSS, Exploit-DB, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Jan 8, 2024

EPSS

100%

top of FIRST's scoreset

Affects

Joomla! Project

Joomla! CMS

CVSS base

5.3

medium

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

Yes

can an attacker script all four kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade Joomla! CMS to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

CISA required action

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

Federal deadline Jan 29, 2024 — passed 956 days ago

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Treat as emergency remediation because CISA KEV status is present.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
Joomla! Project	Joomla! CMS	4.0.0-4.2.7	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

None

Confidentiality

Low

Integrity

None

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
5.3	CVSS 3.1	medium	3.9	1.4	NVD, CNA

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-284 · Improper Access Control

Varies by Context::

Mitigation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.

Weakness & attack patterns

CWE-284Improper Access Control

Inferred from the weakness class — not observed against this CVE.

CAPEC-1 · Accessing Functionality Not Properly Constrained by ACLsCAPEC-122 · Privilege Abuse

T1027.009Obfuscated Files or Information: Embedded Payloads
T1546.004Event Triggered Execution: .bash_profile and .bashrc
T1546.016Event Triggered Execution: Installer Packages

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

CISAThat month →

Listed

Jan 8, 2024

Federal deadline

Jan 29, 2024

passed 956 days ago

Ransomware use

Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

109

1 of the 5 sampled are weaponized

Exploit entries

Exploit-DB and CTI exploit indexes

Social mentions

Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.

4 more posts on this CVEShowing 5 of 9 · Who is discussing this CVE, and how loudlyUnlock free

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable Joomla! CMS.
Monitor for scanner or exploit-pattern traffic after 151 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPS

Groups associated with this CVE

Groups reported in connection with this vulnerability. A reported association, not a confirmed observation of that group using it — and not scoped to any sector or campaign.

hash334e32e7eea638089a7259c594d87db965
SOCRadar Threat Exchange Services · Jul 11, 2026
hashb05579c5144602216ce0787cf1161bb60a67e9e265
SOCRadar Threat Exchange Services · Jul 11, 2026
hash49152:deurfqriidw7kamngrs7qibb8gdcdomsu+zomwghvls3uewtzkcfz6gc7ppyziil:c+vq5pmgcpv+
SOCRadar Threat Exchange Services · Jun 29, 2026

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Cve is exploited BardLaudian/CVE-2023-23752
Jul 21, 2026 · SOCRadar CTI
Cve is exploited Marwan651/Joomla-CMS-Full-Lifecycle-Pentest
Jul 21, 2026 · SOCRadar CTI
Added · CVSS 3.1 5.3 (AV:N)
Jun 17, 2026 · NVD
2025
Bulletin released on NIST.
Oct 16, 2025 · SOCRadar CTI
Bulletin released on NIST.
Oct 16, 2025 · SOCRadar CTI
Bulletin released on NIST.
Feb 7, 2025 · SOCRadar CTI
2024
CVE is exploited. "Aureum01/CVE-2023-23752"
Aug 11, 2024 · SOCRadar CTI
Added to CISA KEV catalog
Jan 8, 2024 · CISA
2023
Added · Verified webapps entry: Joomla! v4.2.8 - Unauthenticated information disclosure
Apr 8, 2023 · Exploit-DB
Initial · CVE published
Feb 16, 2023 · NVD

Source activity

Readings a source repeats on a schedule, counted rather than listed.

9×TweetsSep 2, 2025 – May 23, 2026 · SOCRadar CTI
7×SVRS was changedMay 6, 2025 – Jul 21, 2026 · SOCRadar CTI
6×Github ReposMay 5, 2025 – Jul 17, 2026 · SOCRadar CTI
1×CVE appeared in the Cve Trends.Jan 4, 2026 · SOCRadar CTI

References

4 on the record

developer.joomla.org/security-centre/894-20230201-core-improper-access-check-in-webservice-endpoints.html
Vendor Advisory, NIST
www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2023-23752
US Government Resource
www.exploit-db.com/exploits/51334
Vendor Advisory
nvd.nist.gov/vuln/detail/CVE-2023-23752
Vendor Advisory

Coverage

4 stories from the feeds we poll

Elsewhere on this site

Joomla! Projectevery CVE for this vendor
January 2024what else CISA listed
Access Controlsame class
CWE-284other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

Only the 3 indicator(s) reported for this CVE are available; no packet-level or host-forensic artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2023-23752 is [20230201] - Core - Improper access check in webservice endpoints, a medium vulnerability affecting Joomla! CMS from Joomla! Project. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 151 public PoC repositories reported; 1 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 5.3 describes technical severity, while EPSS 100% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.