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

> Authenticated attackers can inject malicious scripts into product names, leading to JavaScript execution and potential account takeover in other users' browsers.

- **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:** 22 Sep 2025
- **Updated:** 24 Sep 2025
- **Also known as:** GHSA-q7jf-phpc-j8cf

## What is CVE-2025-57204?

CVE-2025-57204 is a medium-severity cross-site scripting vulnerability in n/a, published on 22 Sep 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

Stocky POS with Inventory Management & HRM (ui-lib) version 5.0 is affected by a Stored Cross-Site Scripting (XSS) vulnerability within the Products module available to authenticated users. The vulnerability resides in the product name parameter submitted to the product-creation endpoint via a standard POST form. Due to insufficient input sanitization and output encoding, attackers can inject HTML/JS payloads. The payload is stored and subsequently rendered unsanitized in downstream views, leading to JavaScript execution in other users' browsers when they access the affected product pages. This issue allows an authenticated attacker to execute arbitrary JavaScript in the context of another user, potentially enabling session hijacking, privilege escalation within the application, data exfiltration, or administrative account takeover. The application also lacks a restrictive Content Security Policy (CSP), increasing exploitability.

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

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

It affects 1 product.


Products: Ui-Lib Stocky.

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

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

## Is CVE-2025-57204 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-57204 is a medium-severity cross-site scripting vulnerability in n/a, published on 22 Sep 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-57204 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-57204/ (Markdown: https://insights.sbomify.com/CVE-2025-57204/index.md)
```

## Sources

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

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