# CVE-2021-24328: WP Login Security and History <= 1.0 - CSRF to Stored Cross-Site Scripting (XSS)

> Attackers can exploit CSRF to inject stored XSS payloads into plugin settings, allowing code execution in admin sessions.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Jun 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-3fcr-4vvp-335p

## What is CVE-2021-24328?

CVE-2021-24328 is a medium-severity cross-site scripting vulnerability in Unknown WP Login Security and History, published on 1 Jun 2021. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

The WP Login Security and History WordPress plugin through 1.0 did not have CSRF check when saving its settings, not any sanitisation or validation on them. This could allow attackers to make logged in administrators change the plugin's settings to arbitrary values, and set XSS payloads on them as well

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Clogica Wp Login Security and History.

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

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

## Is CVE-2021-24328 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-24328 is a medium-severity cross-site scripting vulnerability in Unknown WP Login Security and History, published on 1 Jun 2021. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-24328 in the wild and no public exploit code.

Affected product: Unknown WP Login Security and History. 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-24328/ (Markdown: https://insights.sbomify.com/CVE-2021-24328/index.md)
```

## Sources

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

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