Skip to main content
VulnerabilityPublished

CVE-2025-54297: compojoom.com CComment component for Joomla · Cross-site Scripting

Affects compojoom.com CComment component for JoomlaSource CVE Database V5

0

Not known to be exploited · CVSS 7.0 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score
7.0High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Jul 2025

  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
compojoom.com CComment component for JoomlaAffected
  • =5.0.0-6.1.14
Fixed in–

AI-suggested

European organizations should immediately audit their Joomla installations to identify the presence of the CComment component within the affected version range (5.0.0 to 6.1.14). Until an official patch is released, organizations should implement strict input validation and output encoding on all user-generated content fields, especially comments, to neutralize potentially malicious scripts. Web Application Firewalls (WAFs) should be configured with rules to detect and block typical XSS payloads targeting comment sections. Administrators should enforce the principle of least privilege, limiting high-level access to trusted personnel only, and monitor logs for suspicious comment submissions or administrative actions. User awareness training should emphasize the risks of interacting with suspicious content. Additionally, organizations should consider temporarily disabling the CComment component or replacing it with alternative, secure commenting solutions. Regular backups and incident response plans should be updated to address potential exploitation scenarios.

Description

A stored XSS vulnerability in CComment component 5.0.0-6.1.14 for Joomla was discovered.

References

Community reviews

Loading reviews…