Read the docs
TI-2021-06828 Aliases CVE-2021-24543GHSA-c2qq-rpxf-6qmx

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

Priority LOW 27CWE-352Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
Required
Attack complexity
Low
Impact type
Tampering, Cross-site scripting
Confidentiality · integrity · availability
Low · Low · None
Fix status
No fix listed

Attack profile from CVSS 3.1 · NVD. Fix status from CNA. Impact type from CWE-352 and CWE-79.

Summary

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 it matters now

EPSS 0.00412 35th percentileScored 2026-11-07
Public exploit Yes 1 exploit referenceTagged by NVD
Fix No fix listed No fixed version in the sources yet

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
UnknownjQuery Reply to Comment1.31 – 1.31—No fix listedCNA
  • jQuery Reply to Comment VendorUnknown Affected 1.31 – 1.31 Fixed in — No fix listed CNA

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:jquery-reply-to-comment_project:jquery-reply-to-comment:*:*:*:*:*:wordpress:*:*up to 1.31VulnerableJquery-reply-to-comment Project

Remediation

No fixed version listed by the sources yet.

Timeline

  1. 2026-10-02 Threatist record created from CVE-2021-24543
  2. 2026-10-03 Alias added: GHSA-c2qq-rpxf-6qmx

References

Sources