jQuery Reply to Comment: Cross-site scripting
jQuery Reply to Comment is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
- Component
- jQuery Reply to Comment
- Plugin slug
jquery-reply-to-comment- Affected
- See vendor advisory
- Safe version
- See mitigation notes
- Published
- Oct 25, 2021
This CVE was published Oct 25, 2021 and is one of 1 known issue for this plugin.
Update, patch or deactivate.
Update jQuery Reply to Comment to a release outside the affected range, or disable and remove it until a fixed version is available.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical 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.
NVD vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N