CVE-2021-24543: The jQuery Reply to Comment WordPress plugin through 1.31 does not have any CSRF check when saving its setting

Q: How do I fix CVE-2021-24543?

jquery-reply-to-comment: upgrade to newer than 1.31. Exact commands for each OS are on this page.

Q: Is CVE-2021-24543 being exploited?

CVE-2021-24543 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2021-24543 affect?

CVE-2021-24543 affects jquery-reply-to-comment. Severity is medium (CVSS 6.1). 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 C

Q: How urgent is CVE-2021-24543?

Priority 35/100. Public exploit reference

Routine

MEDIUM 6.1UPGRADE

CVE-2021-24543 is a medium-severity flaw (CVSS 6.1) affecting jquery-reply-to-comment. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	6.1 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.4% (top 65%)
CISA exploited list	No
Weakness	CWE-79, CWE-352
Published	2021-10-25
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: jquery-reply-to-comment project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2021-10-25 14:15 UTCPublished CVE record published
2026-06-17 03:40 UTCUpdated Record last modified

jquery-reply-to-comment project jquery-reply-to-comment UPGRADE

Affected: <= 1.31

Fixed in: newer than 1.31

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy jquery-reply-to-comment || rpm -q jquery-reply-to-comment || jquery-reply-to-comment --version

2. UPGRADE to newer than 1.31 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade jquery-reply-to-comment

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade jquery-reply-to-comment

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2021-24543?

jquery-reply-to-comment: upgrade to newer than 1.31. Exact commands for each OS are on this page.

Is CVE-2021-24543 being exploited?

CVE-2021-24543 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2021-24543 affect?

CVE-2021-24543 affects jquery-reply-to-comment. Severity is medium (CVSS 6.1). 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 C

How urgent is CVE-2021-24543?

Priority 35/100. Public exploit reference

Software pages

WordPress vulnerabilities · jQuery vulnerabilities

References

← Back to latest CVEs