VulnerabilityPublished 13 Jul 2026

CVE-2026-47677: FacturaScripts · Account takeover of any 2FA-enabled user

Affects facturascripts/facturascriptsSource GCVE Database

Compare

Not known to be exploited · CVSS 9.3 Critical : upgrade to 2026.3 as a priority.

Data as of 14 Jul 2026, 09:45 UTC

CVSS 4.0 base score

9.3Critical

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 2026.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

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: High
Vulnerable system integrity: High
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the vulnerable system. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the vulnerable system.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade facturascripts/facturascripts to 2026.3.

Affected software

Product	Affected	Fixed in
Packagistfacturascripts/facturascripts	Affected <2026.3	Fixed in 2026.3

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

AI-suggested

If you cannot patch yet, users should consider disabling 2FA or restricting access to the vulnerable endpoint if possible. Monitoring for unusual authentication attempts and applying external rate limiting may help mitigate brute force attacks. Avoid exposing the 2FA validation endpoint publicly. Follow vendor updates closely for an official patch or temporary mitigations.

Description

FacturaScripts contains a critical authentication bypass vulnerability in its two-factor authentication (2FA) validation endpoint. The endpoint accepts unauthenticated POST requests with only a username and TOTP code, without verifying the user's password or requiring CSRF protection. It also lacks rate limiting, allowing brute force attacks against the 2FA codes. Due to an extended verification window, multiple valid codes exist simultaneously, making brute forcing feasible within minutes. Successful exploitation results in complete account takeover of any 2FA-enabled user, including administrators. The vulnerability affects versions prior to 2026.3 and has a CVSS 4.0 base score of 9.3 (critical).

Impact

An unauthenticated remote attacker can completely bypass two-factor authentication and gain full access to any 2FA-enabled user account by brute forcing valid TOTP codes. This includes administrative accounts, which typically have publicly guessable usernames. The attacker gains full read and write privileges as the compromised user, potentially exposing sensitive data and allowing unauthorized actions. The vulnerability also enables targeted denial-of-service by locking out legitimate users after repeated failed attempts. The overall impact is critical, compromising confidentiality and integrity with minimal availability impact.

Summary

The vulnerability exists in FacturaScripts' Core/Controller/Login.php method twoFactorValidationAction(), which processes 2FA validation without requiring password verification or CSRF tokens, and without rate limiting. The verification window for TOTP codes is set to 8, allowing approximately 17 valid codes at once, increasing the chance of guessing a valid code. An attacker who knows a target's username (nick) can brute force the 2FA code via unauthenticated POST requests to /login?action=two-factor-validation. This leads to full session cookie issuance and complete account takeover. The vulnerability is present in all versions before 2026.3. A public proof-of-concept exploit exists demonstrating the attack.

CWE-287Improper Authentication (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Libraries or Frameworks
Use an authentication framework or library such as the OWASP ESAPI Authentication feature.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
V9.2.3 (opens in a new tab)
Attack patterns
Fake the Source of Data (opens in a new tab)
Utilizing REST's Trust in the System Resource to Obtain Sensitive Data (opens in a new tab)
Session Hijacking (opens in a new tab)
Token Impersonation (opens in a new tab)
Upload a Web Shell to a Web Server (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Jul 2026, 09:45 UTC

WeaknessesCWE-287

Technical details

References

Community reviews

Related threats