CVE-2025-12628VulnerabilityPublished 24 Nov 2025

CVE-2025-12628: WP 2FA · Insufficient Entropyy

Affects WP 2FASource CVE Database V5

Not known to be exploited · CVSS 6.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

6.3Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: Low

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, 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: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
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 impacted component 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 impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 2026-10-26.

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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC 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

Affected software

Product	Affected	Fixed in
WP 2FA	Affected =0	Fixed in–

AI-suggested

1. Immediately audit the use of WP 2FA plugin across all WordPress installations and identify affected versions. 2. Until an official patch is released, consider disabling backup code functionality or restricting its use to minimize attack surface. 3. Enhance monitoring and alerting on authentication attempts, especially repeated failed backup code entries, to detect brute force attempts early. 4. Encourage users to regenerate backup codes once a fix is available, ensuring new codes are generated with sufficient entropy. 5. Evaluate alternative 2FA plugins with proven secure random number generation and entropy sources as a temporary or permanent replacement. 6. Implement network-level protections such as rate limiting and IP blacklisting to hinder brute force attacks against backup codes. 7. Conduct code reviews and security testing on custom or third-party plugins to verify cryptographic strength of random number generation. 8. Educate administrators and users on the risks of weak backup codes and the importance of safeguarding 2FA credentials. 9. Maintain up-to-date backups and incident response plans to quickly recover from potential compromises. 10. Engage with the WP 2FA plugin developers or community to track patch releases and apply updates promptly.

Description

The WP 2FA WordPress plugin does not generate backup codes with enough entropy, which could allow attackers to bypass the second factor by brute forcing them

Impact

For European organizations, this vulnerability poses a tangible risk to the security of WordPress-based websites and services, especially those relying on WP 2FA for multi-factor authentication. Successful exploitation could allow attackers to bypass the second authentication factor, leading to unauthorized administrative access. This can result in data breaches, website defacement, injection of malicious content, or disruption of services. Given the medium severity, the confidentiality, integrity, and availability of affected systems could be compromised to a limited extent but still with potentially serious consequences for business operations and customer trust. Organizations in sectors such as e-commerce, government, media, and finance that use WordPress extensively are particularly at risk. The absence of known exploits reduces immediate threat but does not eliminate the risk of future attacks. The vulnerability's exploitation requires low privileges but no user interaction, making it feasible for insiders or attackers who have gained initial access to escalate their control. The impact is magnified in environments where backup codes are widely used or where 2FA is the primary defense against account compromise. Additionally, the lack of a current patch increases exposure time, necessitating proactive risk management.

CWE-331Insufficient Entropy (opens in a new tab)
Base weaknessOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product uses an algorithm or scheme that produces insufficient entropy, leaving patterns or clusters of values that are more likely to occur than others.
Implementation
Determine the necessary entropy to adequately provide for randomness and predictability. This can be achieved by increasing the number of bits of objects such as keys and seeds.
OWASP Cheat Sheets
Session Management (opens in a new tab)
Transport Layer Protection (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
Cryptographic Storage (opens in a new tab)
OWASP ASVS 4.0.3
V3.2.2 (opens in a new tab)
V3.2.4 (opens in a new tab)
V2.3.1 (opens in a new tab)
Attack patterns
Session Credential Falsification through Prediction (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

wpscan.com/vulnerability/5e2d033c-dde6-4774-8588-cbe268c0d797/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 1 Dec 2025, 14:40 UTC

WeaknessesCWE-331

Technical details

References

Community reviews

Related threats