# CVE-2025-55757: Extension - virtuemart.net - XSS in VirtueMart component 1.0.0 - 4.4.10 for Joomla

> Unauthenticated attackers can execute arbitrary scripts in victims' browsers via reflected XSS in the VirtueMart component for Joomla.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Oct 2025
- **Updated:** 28 Oct 2025
- **Also known as:** GHSA-hf3x-mcrv-x4f8

## What is CVE-2025-55757?

CVE-2025-55757 is a medium-severity cross-site scripting vulnerability in virtuemart.net Virtuemart component for Joomla, published on 25 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A unauthenticated reflected XSS vulnerability in VirtueMart 1.0.0-4.4.10 for Joomla was discovered.

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

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


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

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

## Is CVE-2025-55757 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-55757 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-55757 is a medium-severity cross-site scripting vulnerability in virtuemart.net Virtuemart component for Joomla, published on 25 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-55757 exists.

Affected product: virtuemart.net Virtuemart 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-55757/ (Markdown: https://insights.sbomify.com/CVE-2025-55757/index.md)
```

## Sources

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

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