FacturaScripts: Account takeover of any 2FA-enabled user
CVE-2026-47677GHSA-c67f-gmxw-mj93
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (facturascripts/facturascripts 2026.3), 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
- <= 2026.2
- Fixed in
- 2026.3
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-c67f-gmxw-mj93 lists affected ranges: Packagist facturascripts/facturascripts >=0 <=2026.2
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 4.0
- 9.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N · score source
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
Authentication bypass in FacturaScripts: /login?action=two-factor-validation accepts brute-forceable TOTP without password or CSRF protection Summary Core/Controller/Login.php::twoFactorValidationAction() accepts an unauthenticated POST containing only fsNick and fsTwoFactorCode. If the TOTP value matches, the server issues a full fsNick + fsLogkey session cookie pair. The handler: 1. Does not verify the password — the user is not required to have just completed loginAction. 2. Does not call validateFormToken() — no CSRF token is required (every other action handler in the same file does call it). 3. Does not call userHasManyIncidents() before processing — loginAction and changePasswordAction both check this guard before doing work; the 2FA handler only writes to the incident list after a failure, and the incident list is consulted by loginAction / changePasswordAction but not by the 2FA handler itself. The endpoint therefore has no rate-limiting at all. Combined with…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-c67f-gmxw-mj93
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-47677 Advisory: FacturaScripts: Account takeover of any 2FA-enabled user IDs: CVE-2026-47677, GHSA-c67f-gmxw-mj93 Record: https://patchnext.com/advisories/cve-2026-47677 (revision 1, source checked 26 Oct 2026, 14:50 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Critical (CVSS 9.3) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: facturascripts/facturascripts 2026.3. A vendor fix does not mean a deployment is fixed. ## Affected components - Packagist facturascripts/facturascripts: affected <= 2026.2; fixed in 2026.3 ## 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-c67f-gmxw-mj93 (GitHub-reviewed advisory GHSA-c67f-gmxw-mj93 lists affected ranges: Packagist facturascripts/facturascripts >=0 <=2026.2) Commands are suggestions: review each one before running it.
Loading voting…