CVE-2026-35220: Joomla! CMS · Cross-Site Request Forgery (CSRF)
Affects Joomla! CMSSource CVE Database V5
Not known to be exploited · CVSS 4.6 Medium.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 26 May 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 29 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
Project vendor advisory for current remediation guidance. Until an official fix is available, administrators should be cautious with user privileges and consider additional CSRF protections or monitoring for suspicious activity related to the admin activation endpoint.
Description
A Cross-Site Request Forgery (CSRF) vulnerability exists in Joomla! CMS versions 6.0.0 through 6.1.0 due to lack of CSRF token validation in the admin activation endpoint of the com_users component. This vulnerability allows an attacker with high privileges and user interaction to potentially perform unauthorized actions via crafted requests. The CVSS 4.6 score reflects a medium severity level. No official patch or remediation guidance is currently provided by the vendor.