CVE-2026-21629: Joomla! CMS · Improper Access Control
Affects Joomla! CMSSource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 1 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Joomla! ProjectJoomla! CMS | Affected
| Fixed in– |
Packagistjoomla/joomla-cmspkg:composer/joomla/joomla-cmsOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Organizations should immediately review access controls on their Joomla! CMS installations, especially restricting access to administrative ajax endpoints. Until official patches are released, administrators can implement web application firewall (WAF) rules to block unauthorized ajax requests or restrict access to the administrative area by IP address or VPN. It is also advisable to audit third-party extensions that might rely on the ajax component to ensure they do not expose additional risks. Monitoring web server logs for unusual ajax requests and implementing rate limiting can help detect and mitigate exploitation attempts. Once Joomla! releases patches addressing this vulnerability, organizations should prioritize timely updates. Additionally, following the principle of least privilege for administrative accounts and enforcing strong authentication mechanisms can reduce the risk of exploitation.
Description
The ajax component was excluded from the default logged-in-user check in the administrative area. This behavior was potentially unexpected by 3rd party developers.