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

> An authenticated attacker can inject malicious scripts via customer names in LionCoders SalePro POS, leading to script execution in other users' browsers.

- **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:** 6 Oct 2025
- **Updated:** 6 Oct 2025
- **Also known as:** GHSA-wc39-m28p-qq2v

## What is CVE-2025-56382?

CVE-2025-56382 is a medium-severity cross-site scripting vulnerability in n/a, published on 6 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 stored Cross-site scripting (XSS) vulnerability exists in the Customer Management Module of LionCoders SalePro POS 5.4.8. An authenticated attacker can inject arbitrary web script or HTML via the 'Customer Name' parameter when creating or editing customer profiles. This malicious input is improperly sanitized before storage and subsequent rendering, leading to script execution in the browsers of users who view the affected customer details.

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

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

It affects 1 product.


Products: Lion-Coders Salepro Pos.

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

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

## Is CVE-2025-56382 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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