# CVE-2021-24982: Child Theme Generator <= 2.2.7 - Reflected Cross-Site Scripting

> Attackers can inject malicious scripts into the admin dashboard via the parade parameter, potentially compromising administrator accounts.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Mar 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-v9hx-6rmh-g3mr

## What is CVE-2021-24982?

CVE-2021-24982 is a medium-severity cross-site scripting vulnerability in Unknown Child Theme Generator, published on 14 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Child Theme Generator WordPress plugin through 2.2.7 does not sanitise escape the parade parameter before outputting it back, leading to a Reflected Cross-Site Scripting in the admin dashboard

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

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

It affects 1 product.


Products: Childtheme-Generator Child Theme Generator.

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

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

## Is CVE-2021-24982 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-24982 is a medium-severity cross-site scripting vulnerability in Unknown Child Theme Generator, published on 14 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-24982 in the wild and no public exploit code.

Affected product: Unknown Child Theme Generator. 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-24982/ (Markdown: https://insights.sbomify.com/CVE-2021-24982/index.md)
```

## Sources

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

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