# CVE-2026-23476: FacturaScripts Affected by Reflected XSS

> Attackers can execute arbitrary scripts via reflected XSS in error messages, potentially compromising user sessions in FacturaScripts.

- **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:** Yes
- **Published:** 2 Feb 2026
- **Updated:** 3 Feb 2026
- **Also known as:** GHSA-g6w2-q45f-xrp4

## What is CVE-2026-23476?

CVE-2026-23476 is a medium-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. Prior to 2025.8, there a reflected XSS bug in FacturaScripts. The problem is in how error messages get displayed. Twig's | raw filter is used, which skips HTML escaping. When triggering a database error (like passing a string where an integer is expected), the error message includes the input and gets rendered without sanitization. This vulnerability is fixed in 2025.8.

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

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

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 | 2025.81 |
| `facturascripts/facturascripts` | Packagist | All versions | 2025.81 |

Products: Facturascripts Facturascripts.

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

Upgrade facturascripts/facturascripts to 2025.81 or later.

## Is CVE-2026-23476 being exploited?

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

## 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-23476 and fix it if it is affected.

What it is: CVE-2026-23476 is a medium-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: There is no known exploitation of CVE-2026-23476 in the wild and no public exploit code.

Affected packages and fixed versions:
- facturascripts/facturascripts (Packagist): affected all versions; fixed in 2025.81
- facturascripts/facturascripts (Packagist): affected all versions; fixed in 2025.81

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

## Sources

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

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