CVE-2021-24554 json
Paytm - Donation Plugin <= 1.3.2 - Authenticated (admin+) SQL Injection
published 5y ago modified 4mo ago also EUVD-2021-11466
- cvss
- 7.2
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 6.6%
- EPSS 6.6% chance of exploitation in 30 days, percentile 93%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
The Paytm – Donation Plugin WordPress plugin through 1.3.2 does not sanitise, validate or escape the id GET parameter before using it in a SQL statement when deleting donations, leading to an authenticated SQL injection issue
Is CVE-2021-24554 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
6.62% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Nuclei template WordPress Paytm Donation <=1.3.2 - Authenticated SQL Injection nuclei detection template
- wpscan.com https://wpscan.com/vulnerability/f2842ac8-76fa-4490-aa0c-5f2b07ecf2ad referenced PoC, tagged "exploit" by a source, unverified
- codevigilant.com https://codevigilant.com/disclosure/2021/wp-plugin-wp-paytm-pay/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.5 | AV:N/AC:L/Au:S/C:P/I:P/A:P |
Affected products
- Unknown Paytm – Donation Plugin
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
- Technology feeds
References
-
wpscan.com
/vulnerability/f2842ac8-76fa-4490-aa0c-5f2b07ecf2ad
exploit, third-party-advisory
-
codevigilant.com
/disclosure/2021/wp-plugin-wp-paytm-pay/
exploit, third-party-advisory
Sources
- CVE List CVE-2021-24554
- NVD CVE-2021-24554
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.