Skip to main content
VulnerabilityPublished Updated

CVE-2026-27964: facturascripts/facturascripts · FacturaScripts vulnerable to Reflected Cross-Site Scripting (XSS) via Cookie Manipulation

Affects facturascripts/facturascriptsSource GCVE Database

0
Compare
Authoritative record:CVE-2026-27964· Low 3.9

Not known to be exploited · CVSS 3.9 Low : upgrade to 2025.8 when convenient.

Data as of 30 Oct 2026, 18:33 UTC

CVSS 3.1 base score
3.9Low
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 2025.8, 2025.81
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 30 Oct 2026.

What to do

Upgrade facturascripts/facturascripts to 2025.8; facturascripts/facturascripts to 2025.81.

Affected software

ProductAffectedFixed in
Packagistfacturascripts/facturascriptsAffected
  • <2025.8
Fixed in
  • 2025.8
Packagistfacturascripts/facturascriptsAffected
  • >=2025.11 <2025.81
Fixed in
  • 2025.81

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

### Summary A Reflected Cross-Site Scripting (XSS) vulnerability exists in the fsNick cookie parameter. The application reflects the cookie's value directly into the HTML without sanitization. ### Details The fsNick cookie is rendered into the DOM without encoding. While the server does reject the modified session and forces a logout, the HTML containing the payload reaches the browser first. This lets the script execute immediately upon load, effectively beating the redirect. ### PoC 1. Log in to the application with any valid account. <img width="2078" height="302" alt="image" src="https://github.com/user-attachments/assets/d8a9a779-44e0-4a3e-839f-0a031868fbd5" /> 2. Capture any the GET request . <img width="1267" height="276" alt="image" src="https://github.com/user-attachments/assets/22e43f73-4f86-4cab-a074-7aba584a71ac" /> 3. Modify the value of "fsNick" with the following JavaScript: `<script>alert(window.origin)</script>` 4. Send the modified request. <img width="1569" height="319" alt="image" src="https://github.com/user-attachments/assets/ade88db1-aadc-4c50-9e02-d09888067e98" /> 5. Result <img width="1217" height="771" alt="image" src="https://github.com/user-attachments/assets/5858fe9f-127a-4845-b484-5a7ef4ae2cb4" /> ### Impact The payload executes before the session ends, which could potentially allow for a single unauthorized action before the logout.

References

Community reviews

Loading reviews…