CVE-2022-1683: The amtyThumb WordPress plugin through 4.2.0 does not sanitise and escape a parameter before using it in a SQL

Q: How do I fix CVE-2022-1683?

amtythumb: upgrade to newer than 4.2.0. Exact commands for each OS are on this page.

Q: Is CVE-2022-1683 being exploited?

CVE-2022-1683 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-1683 affect?

CVE-2022-1683 affects amtythumb. Severity is high (CVSS 8.8). 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

Q: How urgent is CVE-2022-1683?

Priority 55/100. High severity; Public exploit reference

This month

HIGH 8.8UPGRADE

CVE-2022-1683 is a high-severity flaw (CVSS 8.8) affecting amtythumb. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	1.5% (top 25%)
CISA exploited list	No
Weakness	CWE-89
Published	2022-06-08
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: amtythumb project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-06-08 10:15 UTCPublished CVE record published
2026-06-17 04:22 UTCUpdated Record last modified

amtythumb project amtythumb UPGRADE

Affected: <= 4.2.0

Fixed in: newer than 4.2.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy amtythumb || rpm -q amtythumb || amtythumb --version

2. UPGRADE to newer than 4.2.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade amtythumb

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade amtythumb

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-1683?

amtythumb: upgrade to newer than 4.2.0. Exact commands for each OS are on this page.

Is CVE-2022-1683 being exploited?

CVE-2022-1683 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-1683 affect?

CVE-2022-1683 affects amtythumb. Severity is high (CVSS 8.8). 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

How urgent is CVE-2022-1683?

Priority 55/100. High severity; Public exploit reference

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs