CVE-2026-23997: NeoRazorX facturascripts · Cross-site Scripting
Affects NeoRazorX facturascriptsSource CVE Database V5
Not known to be exploited · CVSS 8.0 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 2 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| NeoRazorXfacturascripts | Affected
| Fixed in– |
GitHubneorazorx/facturascriptspkg:github/neorazorx/facturascriptsOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Apply official patches or updates from NeoRazorX as soon as they become available to address the XSS vulnerability directly. 2. Until patches are released, restrict access to the History view to only trusted and essential administrative users to minimize exposure. 3. Implement strict input validation on the Observations field to sanitize and reject potentially malicious input before storage. 4. Employ output encoding techniques, such as HTML entity encoding, when rendering user-supplied data in the History view to prevent script execution. 5. Use Content Security Policy (CSP) headers to limit the execution of unauthorized scripts in browsers accessing the application. 6. Conduct regular security audits and penetration testing focused on web application input handling and output encoding. 7. Educate administrators and users about the risks of XSS and encourage cautious behavior when interacting with user-generated content. 8. Monitor logs for unusual activity related to the History view or unexpected script execution attempts. 9. Consider deploying web application firewalls (WAF) with rules targeting XSS attack patterns as an additional protective layer.
Description
CVE-2026-23997 is a high-severity Stored Cross-Site Scripting (XSS) vulnerability affecting FacturaScripts versions 2025.71 and earlier. The flaw exists in the Observations field within the History view, where user input is rendered without proper HTML entity encoding, allowing attackers to inject and execute arbitrary JavaScript in the browsers of administrators viewing the history. Exploitation requires at least limited privileges to input data and some user interaction to trigger the payload. The vulnerability impacts confidentiality, integrity, and availability by enabling session hijacking, credential theft, or administrative account compromise. No known exploits are currently reported in the wild. European organizations using FacturaScripts for ERP and accounting functions are at risk, especially those with administrators accessing the affected History view. Mitigation requires applying patches once available, implementing strict input validation and output encoding, and restricting access to the History view to trusted users. Countries with significant SME adoption of FacturaScripts, such as Spain, Germany, France, Italy, and the UK, are most likely affected due to market penetration and the strategic importance of ERP systems. Given the CVSS 3.