FacturaScripts is Vulnerable to Reflected XSS
CVE-2026-23476GHSA-g6w2-q45f-xrp4
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (facturascripts/facturascripts 2025.81), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Packagist facturascripts/facturascripts
- Affected
- < 2025.81
- Fixed in
- 2025.81
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-g6w2-q45f-xrp4 lists affected ranges: Packagist facturascripts/facturascripts >=0 <2025.81
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 5.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
- EPSS
- CVE-2026-23476: 0.29% estimated exploitation activity in the next 30 days; percentile 21.66 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Reflected XSS via SQL Error Messages Summary A reflected XSS bug has been found in FacturaScripts. The problem is in how error messages get displayed - it's using Twig's | raw filter which skips HTML escaping. When a database error is triggered (like passing a string where an integer is expected), the error message includes all input and gets rendered without sanitization. Attackers can use this to phish credentials from other users since HttpOnly is set on cookies (so stealing cookies directly won't work, but attackers can inject a fake login form). CVSS 6.1 (Medium-High) --- What was Found Where the bug exists in the code: Core/View/Macro/Utils.html.twig, line 27: That | raw is the problem. It tells Twig not to escape anything. How it works So here's what happens: 1. Hhit /EditProducto?code=<svg onload=alert(1) or <img src=x onerror=alert(1) 2. The app tries to look up a product with that "code" 3. PostgreSQL throws an error because <svg onload=alert(1) isn't a valid integer 4. The…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-g6w2-q45f-xrp4
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-23476 Advisory: FacturaScripts is Vulnerable to Reflected XSS IDs: CVE-2026-23476, GHSA-g6w2-q45f-xrp4 Record: https://patchnext.com/advisories/cve-2026-23476 (revision 1, source checked 26 Oct 2026, 14:35 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.4) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: facturascripts/facturascripts 2025.81. A vendor fix does not mean a deployment is fixed. ## Affected components - Packagist facturascripts/facturascripts: affected < 2025.81; fixed in 2025.81 ## Suggested inspection (read-only) - Packagist facturascripts/facturascripts: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on facturascripts/facturascripts. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-g6w2-q45f-xrp4 (GitHub-reviewed advisory GHSA-g6w2-q45f-xrp4 lists affected ranges: Packagist facturascripts/facturascripts >=0 <2025.81) Commands are suggestions: review each one before running it.
Loading voting…