Security readout for executives and security teams
Plain-English summary
This WordPress plugin flaw lets an attacker trick a logged-in site administrator into unknowingly changing WP Security Question settings. It does not allow direct takeover by itself, but it can weaken account-recovery or security-question controls if the plugin is used.
Executive priority
Treat as a moderate website-control issue. Prioritize remediation on externally managed WordPress sites, administrator-heavy environments, and sites relying on this plugin for account security workflows.
Technical view
CVE-2021-4386 is a CSRF issue in WP Security Question through version 1.0.5. The save() function lacks correct nonce validation, allowing forged setting changes when an administrator performs attacker-induced interaction. CVSS is 4.3, integrity impact low.
Likely exposure
Exposure is limited to WordPress sites using the WP Security Question plugin in affected versions up to 1.0.5. The bundle does not prove broader platform exposure.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation. Exploitation requires administrator user interaction, such as clicking a malicious link while authenticated to WordPress.
Researcher notes
The key control failure is missing or incorrect nonce validation around settings persistence. Evidence supports CSRF-based settings modification, not unauthenticated arbitrary code execution. Fixed-version details are not explicit in the supplied bundle.
Mitigation direction
- Inventory WordPress sites for WP Security Question and record installed versions.
- Update or replace the plugin according to vendor or WordPress plugin repository guidance.
- Disable the plugin if a fixed version cannot be confirmed.
- Review and restore plugin settings to approved values.
Validation and detection
- Confirm whether WP Security Question is installed on each WordPress instance.
- Check whether installed versions are 1.0.5 or earlier.
- Review plugin settings for unexpected changes.
- Verify the settings save path includes valid nonce enforcement in the deployed plugin code.
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-4386 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/23f9d758-4b5e-44e5-9f58-a37b01c4ffdb?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/browser/wp-security-questions/trunk/modules/settings/model.settings.php#L34CVE 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.