# CVE-2025-60314: Cross-site scripting in n/a

> An authenticated attacker can inject malicious JavaScript via the product name parameter, leading to arbitrary code execution in the victim's browser.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A: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:** 8 Oct 2025
- **Updated:** 8 Oct 2025
- **Also known as:** GHSA-hr54-vmm8-ccwx

## What is CVE-2025-60314?

CVE-2025-60314 is a medium-severity cross-site scripting vulnerability in n/a, published on 8 Oct 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Configuroweb Sistema Web de Inventario 1.0 is vulnerable to a Stored Cross-Site Scripting (XSS) due to the lack of input sanitization on the product name parameter (Nombre:Producto) allowing an authenticated attacker to inject malicious payloads and execute arbitrary JavaScript.

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

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

It affects 1 product.


Products: Configuroweb Simple Web Inventory System.

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

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

## Is CVE-2025-60314 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-60314 is a medium-severity cross-site scripting vulnerability in n/a, published on 8 Oct 2025. 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-2025-60314 exists.

Affected product: n/a. 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-60314/ (Markdown: https://insights.sbomify.com/CVE-2025-60314/index.md)
```

## Sources

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

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