# CVE-2025-0643: XSS in Narkom Communication Technologies' Pyxis Signage

> Stored XSS in Pyxis Signage allows attackers to inject malicious scripts, potentially leading to code execution or data theft.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Nov 2025
- **Updated:** 6 Jun 2026
- **Also known as:** GHSA-7vf9-246v-9pp3

## What is CVE-2025-0643?

CVE-2025-0643 is a high-severity cross-site scripting vulnerability in Narkom Communication and Software Technologies Trade Ltd. Co. Pyxis Signage, published on 20 Nov 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Narkom Communication and Software Technologies Trade Ltd. Co. Pyxis Signage allows Stored XSS.

This issue affects Pyxis Signage: through 31012025.

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

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


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

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

## Is CVE-2025-0643 being exploited?

There is no known exploitation of CVE-2025-0643 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-0643 is a high-severity cross-site scripting vulnerability in Narkom Communication and Software Technologies Trade Ltd. Co. Pyxis Signage, published on 20 Nov 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-0643 in the wild and no public exploit code.

Affected product: Narkom Communication and Software Technologies Trade Ltd. Co. Pyxis Signage. 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-0643/ (Markdown: https://insights.sbomify.com/CVE-2025-0643/index.md)
```

## Sources

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

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