Security readout for executives and security teams
Plain-English summary
This is a reflected cross-site scripting issue in the WP Hardening WordPress plugin. A crafted request could cause attacker-controlled content from the historyvalue parameter to be output in a JavaScript block. Business risk depends on whether the vulnerable plugin is installed and whether users can be induced to open malicious links.
Executive priority
Prioritize remediation for internet-facing WordPress sites where this plugin is installed. The issue is not documented as actively exploited in the provided sources, but reflected XSS can support phishing, session abuse, or administrative action manipulation when users are targeted.
Technical view
WP Hardening before 1.2.2 failed to sanitize or escape the historyvalue GET parameter before embedding it in JavaScript, causing CWE-79 reflected XSS. The source bundle provides no CVSS score, exploit proof details, affected endpoint, or vendor advisory beyond the WPScan reference.
Likely exposure
Exposure is limited to WordPress sites using WP Hardening – Fix Your WordPress Security versions before 1.2.2. Sites without this plugin, or running a non-vulnerable version, are not indicated as affected by the provided sources.
Exploitation context
The sources do not report active exploitation, and the CVE is not listed as KEV in the provided bundle. Reflected XSS generally requires a victim to open or interact with a maliciously crafted request, but the provided sources do not detail prerequisites.
Researcher notes
The title and description identify versions before 1.2.2 as vulnerable. The bundle’s affected version entry is ambiguous, so validate against WPScan or vendor data before asserting exact fixed-version semantics. No exploit steps, CVSS vector, or endpoint path are provided.
Mitigation direction
- Identify WordPress sites running WP Hardening.
- Upgrade WP Hardening to version 1.2.2 or later.
- Check vendor and WPScan guidance for any updated remediation details.
- Remove the plugin if it is unused or cannot be updated.
Validation and detection
- Inventory WordPress plugins and confirm WP Hardening versions.
- Flag any installation below version 1.2.2.
- Review scanner results against the WPScan vulnerability reference.
- Check logs for unusual requests containing the historyvalue parameter.
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-24373 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/fcf17278-609f-4f75-8a87-9b4579dee1c8CVE 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.