Security readout for executives and security teams
Plain-English summary
WordPress sites running WP Hardening – Fix Your WordPress Security before 1.2.2 could reflect malicious script content from a crafted URL into a page attribute. If a user follows such a link, browser-side script could run in that user’s session.
Executive priority
Treat this as a routine but real web security fix. Prioritize internet-facing WordPress sites and administrator-heavy environments, but there is no source-backed evidence here of active exploitation or a critical business emergency.
Technical view
The plugin failed to sanitize or escape $_SERVER['REQUEST_URI'] before placing it in an HTML attribute, creating a reflected cross-site scripting issue classified as CWE-79. The source bundle provides no CVSS score, exploit maturity details, or impacted configuration notes beyond versions before 1.2.2.
Likely exposure
Exposure is limited to WordPress installations with the WP Hardening plugin installed at a vulnerable version before 1.2.2. Public-facing sites are more reachable, but exploitation still depends on a user receiving and opening a crafted URL.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation evidence. This is a reflected XSS issue, so realistic abuse usually requires social engineering or another way to get a target user to visit a crafted link.
Researcher notes
The key weakness is unsanitized REQUEST_URI output into an attribute context. The source bundle does not provide proof-of-concept details, CVSS metrics, authentication requirements, or browser-context impact specifics, so exposure confirmation should focus on plugin presence and version.
Mitigation direction
- Inventory WordPress sites for the WP Hardening plugin and installed version.
- Update WP Hardening to version 1.2.2 or later where available.
- If updating is not possible, check vendor guidance for supported mitigations.
- Limit plugin use on sites where it is not operationally required.
- Review web application firewall rules for generic reflected XSS filtering.
Validation and detection
- Confirm whether each WordPress instance has WP Hardening installed.
- Verify the plugin version is 1.2.2 or later.
- Review change records for when the plugin was updated or removed.
- Check logs for unusual request URIs around sensitive user activity.
- Validate remediation through standard vulnerability scanning, not manual exploit attempts.
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-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-24372 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/5340ae4e-95ba-4a69-beb1-3459cac17782CVE reference · x_refsource_CONFIRM
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 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.