CVE-2021-24492 json
Handsome Testimonials & Reviews < 2.1.1 - Authenticated (Subscriber+) SQL Injection
published 5y ago modified 4mo ago also EUVD-2021-11404
- cvss
- 8.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 75%
- public exploits
- 0
- none known
Summary
The hndtst_action_instance_callback AJAX call of the Handsome Testimonials & Reviews WordPress plugin before 2.1.1, available to any authenticated users, does not sanitise, validate or escape the hndtst_previewShortcodeInstanceId POST parameter before using it in a SQL statement, leading to an SQL Injection issue.
Patch / fix
- handsome_testimonials_&_reviews_project handsome_testimonials_&_reviews 2.1.1
Is CVE-2021-24492 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
1.60% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- codevigilant.com https://codevigilant.com/disclosure/2021/wp-plugin-handsome-testimonials/ referenced PoC, tagged "exploit" by a source, unverified
- wpscan.com https://wpscan.com/vulnerability/42760007-0e59-4d45-8d64-86bc0b8dacea referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/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 Handsome Testimonials & Reviews
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
- Technology feeds
References
-
codevigilant.com
/disclosure/2021/wp-plugin-handsome-testimonials/
exploit, patch, third-party-advisory
-
wpscan.com
/vulnerability/42760007-0e59-4d45-8d64-86bc0b8dacea
exploit, third-party-advisory
Sources
- CVE List CVE-2021-24492
- NVD CVE-2021-24492
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.