jQuery Reply to Comment <= 1.31 - CSRF to Stored Cross-Site Scripting

published 2021-10-25 5 y ago modified 2026-06-17 4 mo ago also EUVD-2021-11455

cvss: 6.1; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 35%
public exploits: 0; none known

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.

Exploit prediction

0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

wpscan.com https://wpscan.com/vulnerability/aa23f743-811b-4fd1-81a9-42916342e312 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.1	6.1	CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
NVD	2.0	4.3	AV:N/AC:M/Au:N/C:N/I:P/A:N

Affected products

Unknown jQuery Reply to Comment

Classification

Weakness

CWE-352 Cross-Site Request Forgery
CWE-79 Improper Neutralization of Input During Web Page Generation

Technology feeds

WordPress rss critical rss

References

wpscan.com /vulnerability/aa23f743-811b-4fd1-81a9-42916342e312
exploit, third-party-advisory

Sources

CVE List CVE-2021-24543
NVD CVE-2021-24543

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary