XSS in Jquery-Reply-To-Comment Project
CVE-2021-24543
- CVSS v3
- 6.1 Medium
- Public exploits
- None known
- EPSS
- 0.004 · 36.4th percentile
- Published
- 2021-10-25
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.
Vulnerability class: XSS (Cross-Site Scripting)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 6.1 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N.
- Attack Vector
- Network
AV:N - Attack Complexity
- Low
AC:L - Privileges Required
- None
PR:N - User Interaction
- Required
UI:R - Scope
- Changed
S:C - Confidentiality
- Low
C:L - Integrity
- Low
I:L - Availability
- None
A:N
EPSS exploit prediction
EPSS 0.004, 36.4th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
- Jquery-Reply-To-Comment Project
- Jquery Reply To Comment — versions 1.31
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 1 other repository (20142995/nuclei-templates). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- wpscan.com/vulnerability/aa23f743-811b-4fd1-81a9-42916342e312 (Exploit, Third Party Advisory)