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

> Attackers can inject malicious scripts into client name fields, potentially executing code or stealing data in the Abacre Retail Point of Sale application.

- **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:** 20 Jan 2026
- **Updated:** 20 Jan 2026
- **Also known as:** GHSA-47vw-q2cv-jhr7

## What is CVE-2025-67263?

CVE-2025-67263 is a medium-severity cross-site scripting vulnerability in n/a, published on 20 Jan 2026. 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

Abacre Retail Point of Sale 14.0.0.396 is affected by a stored cross-site scripting (XSS) vulnerability in the Clients module. The application fails to properly sanitize user-supplied input stored in the Name and Surname fields. An attacker can insert malicious HTML or script content into these fields, which, persisted in the database.

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

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

It affects 1 product.


Products: Abacre Retail Point of Sale.

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

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

## Is CVE-2025-67263 being exploited?

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

Public exploit code:

- Abacre Retail Point of Sale 14.0.0.396 is affected by a stored cross-site scripting (XSS) vulnerability in the Clients module. The application fails to properly sanitize user-supplied input stored in the Name and Surname fields. An attacker can insert malicious HTML or script content into these fields, which, is persisted in the database. (github_poc): https://github.com/Smarttfoxx/CVE-2025-67263

## Other vulnerabilities in n/a

- [CVE-2025-67261](https://insights.sbomify.com/CVE-2025-67261/): SQL injection in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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