# CVE-2026-23997: FacturaScripts has a Stored Cross-Site Scripting (XSS) in "Observations" field via History View

> Attackers can inject malicious scripts into the Observations field, leading to arbitrary JavaScript execution in administrators' browsers when viewing history.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 2 Feb 2026
- **Updated:** 3 Feb 2026
- **Also known as:** GHSA-4v7v-7v7r-3r5h

## What is CVE-2026-23997?

CVE-2026-23997 is a high-severity cross-site scripting vulnerability in NeoRazorX facturascripts, published on 2 Feb 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

FacturaScripts is open-source enterprise resource planning and accounting software. In 2025.71 and earlier, a Stored Cross-Site Scripting (XSS) vulnerability was discovered in the Observations field. The flaw occurs in the History view, where historical data is rendered without proper HTML entity encoding. This allows an attacker to execute arbitrary JavaScript in the browser of viewing the history by administrators.

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

## Which versions are affected by CVE-2026-23997?

2 open source packages ship an affected version, including facturascripts/facturascripts. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `facturascripts/facturascripts` | Packagist | All versions to 2025.71 | None |
| `facturascripts/facturascripts` | Packagist | All versions to 2025.71 | None |

Products: Facturascripts Facturascripts.

## How do I fix CVE-2026-23997?

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

## Is CVE-2026-23997 being exploited?

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

## Other vulnerabilities in NeoRazorX facturascripts

- [CVE-2022-1571](https://insights.sbomify.com/CVE-2022-1571/): Cross-site scripting - Reflected in Create Subaccount in neorazorx/facturascripts (critical 9.9)
- [CVE-2022-1715](https://insights.sbomify.com/CVE-2022-1715/): Account Takeover in neorazorx/facturascripts (critical 9.8)
- [CVE-2022-1682](https://insights.sbomify.com/CVE-2022-1682/): Reflected Xss using url based payload in neorazorx/facturascripts (critical 9.4)
- [CVE-2022-1514](https://insights.sbomify.com/CVE-2022-1514/): Stored XSS via upload plugin functionality in zip format in neorazorx/facturascripts (critical 9.0)
- [CVE-2022-1457](https://insights.sbomify.com/CVE-2022-1457/): Store XSS in title parameter executing at EditUser Page & EditProducto page in neorazorx/facturascripts (critical 9.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-23997 and fix it if it is affected.

What it is: CVE-2026-23997 is a high-severity cross-site scripting vulnerability in NeoRazorX facturascripts, published on 2 Feb 2026. 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-2026-23997 exists.

Affected packages and fixed versions:
- facturascripts/facturascripts (Packagist): affected all versions up to 2025.71; no fix listed
- facturascripts/facturascripts (Packagist): affected all versions up to 2025.71; no fix listed

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-2026-23997/ (Markdown: https://insights.sbomify.com/CVE-2026-23997/index.md)
```

## Sources

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

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