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

> Attackers can execute arbitrary JavaScript in victim browsers via unsanitized input in the WP Hardening WordPress plugin.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Jun 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-fvfr-gwjc-3cpp

## What is CVE-2021-24373?

CVE-2021-24373 is a medium-severity cross-site scripting vulnerability in Unknown WP Hardening – Fix Your WordPress Security, published on 21 Jun 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2021-24373?

It affects 1 product.


Products: Getastra Wp Hardening.

## How do I fix CVE-2021-24373?

No fix has been published for CVE-2021-24373 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-24373 being exploited?

There is no known exploitation of CVE-2021-24373 in the wild and no public exploit code.

## Other vulnerabilities in Unknown WP Hardening – Fix Your WordPress Security

- [CVE-2021-24372](https://insights.sbomify.com/CVE-2021-24372/): WP Hardening < 1.2.2 - Reflected XSS via URI (medium 6.1)
- [CVE-2024-6641](https://insights.sbomify.com/CVE-2024-6641/): WP Hardening – Fix Your WordPress Security <= 1.2.6 - Unauthenticated Security Feature Bypass to Username Enumeration (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-24373 and fix it if it is affected.

What it is: CVE-2021-24373 is a medium-severity cross-site scripting vulnerability in Unknown WP Hardening – Fix Your WordPress Security, published on 21 Jun 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-24373 in the wild and no public exploit code.

Affected product: Unknown WP Hardening – Fix Your WordPress Security. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-24373/ (Markdown: https://insights.sbomify.com/CVE-2021-24373/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-24373
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-24373
- OSV: https://osv.dev/vulnerability/CVE-2021-24373

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-24373/
Summaries are generated and may contain mistakes; the official description above is the record.