Quick answers
- Is CVE-2026-45693 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45693 being exploited in the wild.
- How severe is CVE-2026-45693?
- High severity, with a CVSS score of 7.5, published 14 July 2026.
- Which products and versions are affected?
- NeoRazorX FacturaScripts <= 2026.2; facturascripts/facturascripts (Packagist) <= 2026.2, ECOSYSTEM:introduced=0,last_affected=2026.2.
- Is there a fix for CVE-2026-45693?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-45693 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-45693?
- Check whether you run NeoRazorX FacturaScripts or facturascripts/facturascripts (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A path traversal vulnerability exists in FacturaScripts' static file controllers, specifically 'Core/Controller/Files.php' and 'Core/Controller/Myfiles.php'. The application validates access by performing prefix checks (strpos/substr) on the raw URL string rather than the canonicalized filesystem path. An attacker can use '../' segments in a request starting with an allow-listed prefix (e.g., '/Plugins/') to access files in restricted directories like 'MyFiles/Private/'. This bypasses the 'myft' token requirement for private files, provided the file extension is on the allowed list (pdf, sql, zip, etc.). The vulnerability is confirmed in version 2026.2 and the master branch.
Affected products
- NeoRazorX FacturaScripts <= 2026.2
Identifiers
- CVE-2026-45693
- GHSA-cv65-7cg8-r623
Timeline
- 2026-05-11: other: Vulnerability confirmed on master branch commit de01369
- 2026-07-14: advisory: GitHub Advisory published