CVE-2022-1683 json
amtyThumb <= 4.2.0 - Subscriber+ SQLi
published 4y ago modified 4mo ago also EUVD-2022-24968
- cvss
- 8.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.5%
- EPSS 1.5% chance of exploitation in 30 days, percentile 75%
- public exploits
- 0
- none known
Summary
The amtyThumb WordPress plugin through 4.2.0 does not sanitise and escape a parameter before using it in a SQL statement via its shortcode, leading to an SQL injection and is exploitable by any authenticated user (and not just Author+ like the original advisory mention) due to the fact that they can execute shortcodes via an AJAX action
Is CVE-2022-1683 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.55% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- wpscan.com https://wpscan.com/vulnerability/359d145b-c365-4e7c-a12e-c26b7b8617ce referenced PoC, tagged "exploit" by a source, unverified
- bulletin.iese.de https://bulletin.iese.de/post/amtythumb_4-2-0 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 amtyThumb
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
- Technology feeds
References
-
wpscan.com
/vulnerability/359d145b-c365-4e7c-a12e-c26b7b8617ce
exploit, third-party-advisory
-
bulletin.iese.de
/post/amtythumb_4-2-0
exploit, third-party-advisory
Sources
- CVE List CVE-2022-1683
- NVD CVE-2022-1683
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.