# CVE-2021-24543: jQuery Reply to Comment <= 1.31 - CSRF to Stored Cross-Site Scripting

> Attackers can inject malicious scripts via unsanitized settings, leading to stored XSS and potential session hijacking in the jQuery Reply to Comment 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:** 25 Oct 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-c2qq-rpxf-6qmx

## What is CVE-2021-24543?

CVE-2021-24543 is a medium-severity cross-site scripting vulnerability in Unknown jQuery Reply to Comment, published on 25 Oct 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 jQuery Reply to Comment WordPress plugin through 1.31 does not have any CSRF check when saving its settings, nor sanitise or escape its 'Quote String' and 'Reply String' settings before outputting them in Comments, leading to a Stored Cross-Site Scripting issue.

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

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

It affects 1 product.


Products: Jquery-Reply-to-Comment Project Jquery-Reply-to-Comment.

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

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

## Is CVE-2021-24543 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-24543 is a medium-severity cross-site scripting vulnerability in Unknown jQuery Reply to Comment, published on 25 Oct 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-24543 in the wild and no public exploit code.

Affected product: Unknown jQuery Reply to Comment. 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-24543/ (Markdown: https://insights.sbomify.com/CVE-2021-24543/index.md)
```

## Sources

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

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