Skip to main content
VulnerabilityPublished

CVE-2025-63083: 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
  • =3.9.0-5.4.1
  • =6.0.0-6.0.1
Fixed in–
Packagistjoomla/joomla-cmspkg:composer/joomla/joomla-cmsOther threatsAffected
  • =3.9.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 official channels for security patches addressing CVE-2025-63083 and apply updates promptly once available.
  2. In the interim, restrict access to the pagebreak plugin functionality to only trusted, high-privilege users to minimize exploitation risk.
  3. Implement strict input validation and output encoding on all user-supplied data, especially within custom extensions or templates interacting with the pagebreak plugin.
  4. Deploy Web Application Firewalls (WAFs) with custom rules to detect and block suspicious script injection patterns targeting Joomla! CMS pages.
  5. Conduct regular security audits and penetration testing focusing on XSS vectors in Joomla! installations.
  6. Educate administrators and users about phishing and social engineering risks associated with XSS attacks.
  7. Review and enforce the principle of least privilege for Joomla! user roles to limit the number of users with high privileges required for exploitation.
  8. Consider isolating Joomla! CMS instances in segmented network zones to reduce lateral movement if compromise occurs.

Description

Lack of output escaping leads to a XSS vector in the pagebreak plugin.

References

Community reviews

Loading reviews…