Skip to content
Fencer Vulns
medium 5.3

CVE-2023-23752 kev in the critical feed json

[20230201] - Core - Improper access check in webservice endpoints

published 2023-02-16 3 y ago modified 2026-09-08 2 mo ago also BIT-joomla-2023-23752 , EUVD-2023-27838

cvss
5.3
version 3.1, CNA
cisa kev
Exploited
added 2024-01-08
epss
99.8%
EPSS 99.8% chance of exploitation in 30 days, percentile 99.9%
public exploits
2
Metasploit, Exploit-DB, plus a Nuclei check

Summary

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

Patch / fix

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

  • bitnami joomla 4.2.8
  • joomla joomla! 4.2.8

Timeline

  1. First public exploit (Metasploit auxiliary/scanner/http/joomla_api_improper_access_checks)
  2. Published
  3. Added to CISA KEV
  4. CISA patch deadline
  5. CISA SSVC: exploitation active

Known exploited

Added
2 y ago
Patch by
2024-01-29 (2 y ago)
Ransomware
Not known
Required action
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Vendor, product
Joomla!, Joomla!
CISA name
Joomla! Improper Access Control Vulnerability

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
yes
Technical impact
partial
Assessed
2 y ago

Exploit prediction

99.81% chance of exploitation in the next 30 days, higher than 99.9% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

CVSS scores

assigned by version score vector
CISA ADP 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OSV 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
bitnami joomla
>=4.0.0, <4.2.8
4.2.8

Affected products

  • Joomla! Project Joomla! CMS
  • joomla joomla\!

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.