# CVE-2021-47873: VestaCP < 0.9.8-25 - Stored Cross-Site Scripting

> Attackers can inject malicious scripts via the IP interface configuration, potentially leading to code execution or account takeover in VestaCP.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/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:** 21 Jan 2026
- **Updated:** 5 Mar 2026
- **Also known as:** GHSA-f955-hgxq-hv82

## What is CVE-2021-47873?

CVE-2021-47873 is a medium-severity cross-site scripting vulnerability in VestaCP, published on 21 Jan 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

VestaCP versions prior to 0.9.8-25 contain a cross-site scripting vulnerability in the IP interface configuration that allows attackers to inject malicious scripts. Attackers can exploit the 'v_interface' parameter by sending a crafted POST request to the add/ip/ endpoint with a stored XSS payload.

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

## Which versions are affected by CVE-2021-47873?


## How do I fix CVE-2021-47873?

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

## Is CVE-2021-47873 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-47873 and fix it if it is affected.

What it is: CVE-2021-47873 is a medium-severity cross-site scripting vulnerability in VestaCP, published on 21 Jan 2026. Any signed-in user can exploit it over the network, 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-2021-47873 exists.

Affected product: VestaCP. 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-2021-47873/ (Markdown: https://insights.sbomify.com/CVE-2021-47873/index.md)
```

## Sources

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

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