Security readout for executives and security teams
Plain-English summary
WP Editor before 1.2.7 allowed a logged-in administrator to save plugin settings in a way that could manipulate database queries. The attacker already needs high WordPress privileges, but successful abuse could expose, alter, or disrupt site data.
Executive priority
Prioritize remediation on WordPress sites where many users hold administrator access, admin accounts lack MFA, or site data is business-critical. The privilege requirement lowers broad exposure, but impact after admin compromise is serious.
Technical view
The issue is an authenticated admin-level blind SQL injection in unsanitized or unvalidated WP Editor setting fields during settings save. The CVSS 3.1 score is 7.2, reflecting network access, low complexity, high privileges, no user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to WordPress sites running the WP Editor plugin before 1.2.7 where an attacker has admin-level access or can compromise such an account.
Exploitation context
The supplied WPScan reference is tagged as exploit-related, but the bundle does not show CISA KEV listing or confirmed active exploitation. Treat this as a high-impact post-authentication risk, not proven internet-wide exploitation.
Researcher notes
The sources identify CWE-89 and a blind SQL injection path through settings handling. Public detail in the supplied bundle is limited; avoid assuming affected forks, unauthenticated reachability, or active exploitation beyond the cited WPScan metadata.
Mitigation direction
- Upgrade WP Editor to version 1.2.7 or later.
- Disable or remove WP Editor if it is not required.
- Restrict WordPress administrator access to trusted users only.
- Review admin accounts for weak, unused, or unexpected access.
- Check vendor and WPScan guidance for any additional remediation.
Validation and detection
- Inventory WordPress sites for the WP Editor plugin.
- Confirm installed WP Editor versions are 1.2.7 or later.
- Review logs for unusual plugin settings-save activity by administrators.
- Audit recent database changes if suspicious admin activity exists.
- Verify administrator accounts and MFA posture.
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-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. 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 lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2021-24151 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
- High
- CVSS
- 7.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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:H/UI:N/S:U/C:H/I:H/A:H1.25.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.2HighVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://wpscan.com/vulnerability/5ee77dd7-5a73-4d4e-8038-23e6e763e20c/CVE reference · exploit, vdb-entry
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.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.