Security readout for executives and security teams
Plain-English summary
Blue Admin for WordPress through version 21.06.01 can store unsafe content in its Logo Title setting. Because saving settings lacks CSRF protection, an attacker may be able to trick an authenticated administrator into saving malicious content that later runs in users' browsers.
Executive priority
Act promptly if Blue Admin is present, but this is not a universal WordPress emergency. The business risk is account-assisted browser compromise and possible content tampering through an admin-targeted CSRF path.
Technical view
The flaw combines missing output sanitization/escaping for the Logo Title setting with missing CSRF checks on settings updates. The result is stored XSS reachable through a forced settings change by an authenticated administrator's browser. Public sources do not provide CVSS, a fixed version, or confirmed exploitation.
Likely exposure
Exposure is limited to WordPress sites using the Blue Admin plugin through 21.06.01, especially where administrators can be targeted through email or web links. Sites not running this plugin are not indicated as affected by the supplied sources.
Exploitation context
The bundle does not show KEV listing or confirmed active exploitation. The described attack depends on an authenticated administrator interacting with attacker-controlled content, then the stored value being rendered by the plugin without safe escaping.
Researcher notes
Key gaps are severity scoring, fixed-version status, and exploitation evidence. The CVE maps to CWE-352 and CWE-79. Validate only in owned environments and focus on inventory, affected-version confirmation, stored setting review, and whether output is safely escaped in current code.
Mitigation direction
- Inventory WordPress sites for Blue Admin installations and versions.
- Remove or disable Blue Admin where it is not required.
- Check WPScan and vendor guidance for any patched release or replacement advice.
- Treat Blue Admin settings changes as sensitive administrative activity.
- Review the Logo Title setting for unexpected HTML or script-like content.
Validation and detection
- Confirm whether Blue Admin is installed on each WordPress site.
- Verify installed Blue Admin versions are not through 21.06.01.
- Inspect the Logo Title setting for unauthorized or unsafe content.
- Review administrative activity around Blue Admin settings changes.
- Confirm whether current vendor guidance names a fixed version.
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 lookupCWE-79: 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-24581 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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 and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://wpscan.com/vulnerability/75abd073-b45f-4fe6-8501-7a6d0163f78dCVE reference · x_refsource_MISC
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.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.