Skip to main content
VulnerabilityPublished

CVE-2025-63082: Joomla! CMS · Cross-site Scripting

Affects Joomla! CMSSource CVE Database V5

0

Not known to be exploited · CVSS 5.9 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 11% 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:P/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N/E:U

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Joomla! ProjectJoomla! CMSAffected
  • =4.0.0-5.4.1
  • =6.0.0-6.0.1
Fixed in–
Packagistjoomla/cmspkg:composer/joomla/cmsOther threatsAffected
  • =4.0.0-5.4.1
  • =6.0.0-6.0.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Monitor Joomla! Project announcements closely and apply official patches immediately once released for the affected versions.
  2. Until patches are available, restrict administrative privileges to trusted personnel only and enforce strong authentication mechanisms to reduce the risk of privilege escalation.
  3. Implement strict Content Security Policy (CSP) headers to limit the execution of unauthorized scripts and reduce the impact of XSS attacks.
  4. Use web application firewalls (WAFs) configured to detect and block malicious payloads targeting data URLs in img tags or suspicious script injections.
  5. Conduct regular security audits and code reviews of custom Joomla! extensions or templates that might interact with HTML filtering.
  6. Educate users and administrators about phishing and social engineering risks that could facilitate user interaction required for exploitation.
  7. Disable or limit the use of data URLs in img tags if not necessary for website functionality, reducing the attack surface.
  8. Employ input validation and output encoding best practices in any custom development to complement Joomla!'s filtering mechanisms.

Description

Lack of input filtering leads to an XSS vector in the HTML filter code related to data URLs in img tags.

References

Community reviews

Loading reviews…