Security readout for executives and security teams
Plain-English summary
This CVE affects the WordPress Defender Security plugin through version 2.4.6. A malicious site or link could cause a logged-in administrator’s browser to verify a one-time login without proper request validation. Business impact is limited but relevant because it touches login security controls.
Executive priority
Treat this as a targeted maintenance item, not an emergency. Prioritize affected public WordPress sites where administrators frequently remain logged in, because the issue weakens a login-security function but requires administrator interaction.
Technical view
The issue is CWE-352 CSRF caused by missing or incorrect nonce validation in verify_otp_login_time(). The CVSS 3.1 score is 4.3, with network access, low complexity, no privileges, required user interaction, and low integrity impact only.
Likely exposure
Exposure is likely limited to WordPress sites running Defender Security versions up to and including 2.4.6. Sites without this plugin, or running a fixed newer version, are not indicated as affected by the provided sources.
Exploitation context
The provided sources do not show KEV listing or active exploitation. Exploitation requires tricking a site administrator into taking an action, such as clicking a link, while the vulnerable workflow is reachable.
Researcher notes
Evidence supports a CSRF bypass in a specific Defender Security function. The source bundle does not provide proof of active exploitation, a detailed exploit chain, or a named fixed version beyond the vulnerable range ending at 2.4.6.
Mitigation direction
- Inventory WordPress sites for Defender Security plugin usage and version.
- Update Defender Security beyond version 2.4.6 using vendor-supported releases.
- Review WPMU DEV or WordPress plugin guidance for the confirmed fixed version.
- Limit WordPress administrator accounts to necessary users only.
- Warn administrators against opening untrusted links while authenticated.
Validation and detection
- Confirm whether Defender Security is installed on each WordPress site.
- Record plugin versions and flag any version up to 2.4.6.
- Verify the installed version includes corrected nonce validation for verify_otp_login_time().
- Check vulnerability scanners or Wordfence intelligence for matching findings.
- Review admin activity logs for unusual one-time login verification events.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2021-4425 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/e772fbbe-33d5-46fa-a041-ab07d3f9318f?source=cveCVE reference
- https://blog.nintechnet.com/25-wordpress-plugins-vulnerable-to-csrf-attacks/CVE reference
- https://blog.nintechnet.com/more-wordpress-plugins-and-themes-vulnerable-to-csrf-attacks/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-3/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-2/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-1/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-5/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-4/CVE reference
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=2473684%40defender-security&new=2473684%40defender-security&sfp_email=&sfph_mail=CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.