CVE-2021-24725 json
Comment Link Remove and Other Comment Tools < 2.1.6 - Arbitrary Comment Deletion via CSRF
published 5y ago modified 4mo ago also EUVD-2021-11637
- cvss
- 4.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 42%
- public exploits
- 0
- none known
Summary
The Comment Link Remove and Other Comment Tools WordPress plugin before 2.1.6 does not have CSRF check in its 'Delete comments easily', which could allow attackers to make logged in admin delete arbitrary comments
Patch / fix
- quantumcloud comment_link_remove_and_other_comment_tools 2.1.6
Is CVE-2021-24725 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.49% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- wpscan.com https://wpscan.com/vulnerability/01483284-57f5-4ae9-b5f1-ae26b623571f referenced PoC, tagged "exploit" by a source, unverified
- trustwave.com https://www.trustwave.com/en-us/resources/security-resources/security-advisories/?fid=29225 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Affected products
- Unknown Comment Link Remove and Other Comment Tools
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
- Technology feeds
References
-
wpscan.com
/vulnerability/01483284-57f5-4ae9-b5f1-ae26b623571f
exploit, third-party-advisory
-
trustwave.com
/en-us/resources/security-resources/security-advisories/?fid=29225
exploit, third-party-advisory
Sources
- CVE List CVE-2021-24725
- NVD CVE-2021-24725
Fencer Intel 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.