WP Hardening < 1.2.2 - Reflected XSS via historyvalue
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- Required
- Attack complexity
- Low
- Impact type
- Cross-site scripting
- Confidentiality · integrity · availability
- Low · Low · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA. Impact type from CWE-79.
Summary
The WP Hardening – Fix Your WordPress Security WordPress plugin before 1.2.2 did not sanitise or escape the historyvalue GET parameter before outputting it in a Javascript block, leading to a reflected Cross-Site Scripting issue.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Unknown | WP Hardening – Fix Your WordPress Security | 1.2.2 to before 1.2.2 | 1.2.2 | Patch available | CNA |
- WP Hardening – Fix Your WordPress Security VendorUnknown Affected 1.2.2 to before 1.2.2 Fixed in 1.2.2 Patch available CNA
Remediation
- Fix · CNA WP Hardening – Fix Your WordPress Security (Unknown) Fixed in 1.2.2
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
WP Hardening – Fix Your WordPress Security 1.2.2
2 records Highest priority Priority LOW 2 LOW
Other records, highest priority first
- TI-2021-06664 WP Hardening < 1.2.2 - Reflected XSS via URIPriority LOW 29
Timeline
- 2026-10-02 Threatist record created from CVE-2021-24373
- 2026-10-03 Alias added: GHSA-fvfr-gwjc-3cpp
References
More Getastra Wp Hardening vulnerabilities
- TI-2024-06158 WP Hardening – Fix Your WordPress Security <= 1.2.6 - Unauthenticated Security Feature Bypass to Username Enumeration CVSS 3.1MEDIUM 5.3
- TI-2021-06664 WP Hardening < 1.2.2 - Reflected XSS via URI CVSS 3.1MEDIUM 6.1
Sources
- CVE-2021-24373 · CVE Program
- CVE-2021-24373 · NVD
- FIRST EPSS
- GHSA-fvfr-gwjc-3cpp · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences