# CVE-2026-7170: Stored Cross-Site Scripting (XSS) in TPVEnlanube

> An authenticated attacker can inject malicious scripts into the vendor store name field, leading to code execution in other users' browsers.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-h7w4-9999-mvp8

## What is CVE-2026-7170?

CVE-2026-7170 is a medium-severity cross-site scripting vulnerability in TPVEnlanube Cloud Web application, published on 28 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Stored Cross-Site Scripting (XSS) in TPVEnlanube affecting the following endpoint and parameter:

  *  CVE-2026-7170: parameter 'vendor_store_name' in the endpoint  '/administrator/index.php?pshop_mode=admin&page=store.store_add&option=com_virtuemart&vendor_id=[ID]'.

Successful exploitation of this vulnerability could allow an authenticated attacker to inject malicious code and execute it in users' browsers without their consent.

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

## Which versions are affected by CVE-2026-7170?


## How do I fix CVE-2026-7170?

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

## Is CVE-2026-7170 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-7170 and fix it if it is affected.

What it is: CVE-2026-7170 is a medium-severity cross-site scripting vulnerability in TPVEnlanube Cloud Web application, published on 28 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-7170 in the wild and no public exploit code.

Affected product: TPVEnlanube Cloud Web application. 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-2026-7170/ (Markdown: https://insights.sbomify.com/CVE-2026-7170/index.md)
```

## Sources

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

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