# CVE-2021-24708: WP All Export < 1.3.1 - Admin+ Stored Cross-Site Scripting

> High-privilege users can inject malicious scripts via export names in the WP All Export plugin, potentially compromising admin sessions.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/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:** 8 Nov 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-6fwr-833f-32fw

## What is CVE-2021-24708?

CVE-2021-24708 is a medium-severity cross-site scripting vulnerability in Unknown Export any WordPress data to XML/CSV, published on 8 Nov 2021. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

The Export any WordPress data to XML/CSV WordPress plugin before 1.3.1 does not escape its Export's Name before outputting it in Manage Exports settings, which could allow high privilege users to perform Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed

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

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

It affects 1 product.


Products: Wp All Export Project Wp All Export.

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

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

## Is CVE-2021-24708 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-24708 is a medium-severity cross-site scripting vulnerability in Unknown Export any WordPress data to XML/CSV, published on 8 Nov 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-24708 in the wild and no public exploit code.

Affected product: Unknown Export any WordPress data to XML/CSV. 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-24708/ (Markdown: https://insights.sbomify.com/CVE-2021-24708/index.md)
```

## Sources

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

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