# CVE-2025-54297: Extension - compojoom.com - Stored XSS vulnerability in CComment component 5.0.0-6.1.14 for Joomla

> Attackers can inject malicious scripts via stored XSS in the CComment component, potentially compromising user sessions and data.

- **Severity:** High 7.0 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 23 Jul 2025
- **Updated:** 24 Jul 2025
- **Also known as:** GHSA-vf7x-5mj7-8pgc

## What is CVE-2025-54297?

CVE-2025-54297 is a high-severity cross-site scripting vulnerability in compojoom.com CComment component for Joomla, published on 23 Jul 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

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

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2025-54297?


## How do I fix CVE-2025-54297?

No fix has been published for CVE-2025-54297 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-54297 being exploited?

There is no known exploitation of CVE-2025-54297 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-54297 and fix it if it is affected.

What it is: CVE-2025-54297 is a high-severity cross-site scripting vulnerability in compojoom.com CComment component for Joomla, published on 23 Jul 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-54297 in the wild and no public exploit code.

Affected product: compojoom.com CComment component for Joomla. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-54297/ (Markdown: https://insights.sbomify.com/CVE-2025-54297/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-54297
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-54297
- OSV: https://osv.dev/vulnerability/CVE-2025-54297

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-54297/
Summaries are generated and may contain mistakes; the official description above is the record.