Quick answers
- Is CVE-2026-32699 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-32699 being exploited in the wild.
- How severe is CVE-2026-32699?
- Low severity, with a CVSS score of 3.1, published 5 May 2026.
- Which products and versions are affected?
- NeoRazorX FacturaScripts <= 2025.92; facturascripts/facturascripts (Packagist) ECOSYSTEM:introduced=0,last_affected=2024.92.x-dev.
- Is there a fix for CVE-2026-32699?
- 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-32699 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-32699?
- 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 vulnerability exists in the EditUser controller of FacturaScripts due to improper validation of the 'nick' parameter during POST requests. While the web interface treats the username as an immutable field, the backend processes the form-data parameter without verifying if the value has been altered from its original state. An authenticated attacker can use a proxy to intercept the update request and modify the 'nick' value to rename any account they have access to edit, including the administrator. This leads to a breakdown in accountability and potential corruption of audit trails where the username is used as a unique identifier.
Affected products
- NeoRazorX FacturaScripts <= 2025.92
Identifiers
- CVE-2026-32699
- GHSA-pp79-hqv6-vmc3
Timeline
- 2026-04-27: advisory: GitHub Security Advisory published by vendor
- 2026-05-05: disclosed: CVE published to NVD