How severe is CVE-2025-69210?

No CVSS score has been assigned to CVE-2025-69210 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-69210?

CVE-2025-69210 affects the following packages: facturascripts/facturascripts (Packagist), facturascripts/facturascripts (Packagist), facturascripts/facturascripts (Packagist), facturascripts/facturascripts (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2025-69210?

Update facturascripts/facturascripts to 2025.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-69210 is resolved across your whole dependency graph.

How do I detect CVE-2025-69210 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for facturascripts/facturascripts. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2025-69210 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2025-69210?

O3 pinpoints whether CVE-2025-69210 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2025-69210 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2025-69210, including 1 documented proof-of-concept exploit on Exploit-DB. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What type of vulnerability is CVE-2025-69210?

CVE-2025-69210 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2025-69210 published, and has it been updated?

CVE-2025-69210 was published on December 30, 2025 and was last updated on August 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

CVE-2025-69210

CVE-2025-69210 is a Cross-site Scripting (XSS) vulnerability in facturascripts/facturascripts. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2025-69210 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

FacturaScripts vulnerable to Stored Cross-Site Scripting (XSS) via XML File Upload

Also known asGHSA-2267-xqcf-gw2m

Published

Dec 30, 2025

Updated

Aug 7, 2026

Affected

4 pkgs

Patched

1 / 4

Exploits

1 known

Exploitation data as of Aug 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

4 pkgs affected

🐘facturascripts/facturascripts🐘facturascripts/facturascripts🐘facturascripts/facturascripts🐘facturascripts/facturascripts

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

FacturaScripts is open-source enterprise resource planning and accounting software. Prior to version 2025.7, a stored cross-site scripting (XSS) vulnerability exists in the product file upload functionality. Authenticated users can upload crafted XML files containing executable JavaScript. These files are later rendered by the application without sufficient sanitization or content-type enforcement, allowing arbitrary JavaScript execution when the file is accessed. Because product files uploaded by regular users are visible to administrative users, this vulnerability can be leveraged to execute malicious JavaScript in an administrator’s browser session. Version 2025.7 fixes the issue.

Affected Packages

4 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`facturascripts/facturascripts`	all versions	2025.7
🐘Packagist	`facturascripts/facturascripts`	all versions	No fix
🐘Packagist	`facturascripts/facturascripts`	all versions	No fix
🐘Packagist	`facturascripts/facturascripts`	all versions	No fix

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-52517webappsmultiple

FacturaScripts 2025.43 - XSS

by uvettrivel007 · Apr 29, 2026

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for facturascripts/facturascripts. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update facturascripts/facturascripts to 2025.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-69210 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2025-69210 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2025-69210. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2025-69210 in your dependencies?

O3 detects CVE-2025-69210 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works