What’s Vulnerable › Vulnerabilities
CVE-2026-12106: Auto Upload Images <= 3.3.2 - Authenticated (Contributor+) Server-Side Request Forgery via 'src' Attribute of <img> Tags
- Severity: medium (CVSS 6.4 v3.1)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.3% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2026-09-18 · updated 2026-09-18
- Weakness: CWE-918
Description
The Auto Upload Images plugin for WordPress is vulnerable to Limited Server-Side Request Forgery in all versions up to, and including, 3.3.2 via the downloadImage function. This makes it possible for authenticated attackers, with contributor-level access and above, to make web requests to arbitrary locations originating from the web application. The plugin uses wp_remote_get() rather than wp_safe_remote_get(), and the validate() method only rejects URLs whose host matches the site's own hostname, failing to block requests to private, loopback, or link-local addresses (e.g., 127.0.0.1, 10.0.0.0/8, 169.254.169.254). Attackers can trigger this by embedding a crafted <img> tag with a src attribute pointing to internal network hosts in post content and submitting it for processing.
Affected products
- airani Auto Upload Images: through 3.3.2
References
- https://plugins.trac.wordpress.org/browser/auto-upload-images/tags/3.3.2/src/ImageUploader.php#L192
- https://plugins.trac.wordpress.org/browser/auto-upload-images/tags/3.3.2/src/ImageUploader.php#L48
- https://plugins.trac.wordpress.org/browser/auto-upload-images/tags/3.3.2/src/WpAutoUpload.php#L45
- https://plugins.trac.wordpress.org/browser/auto-upload-images/tags/3.3.2/src/WpAutoUpload.php#L64
- https://plugins.trac.wordpress.org/browser/auto-upload-images/tags/3.3.2/src/WpAutoUpload.php#L96
- https://plugins.trac.wordpress.org/changeset?reponame=&old=3693206%40auto-upload-images&new=3693206%40auto-upload-images
- https://www.wordfence.com/threat-intel/vulnerabilities/id/adda0c06-80c7-4e2b-af18-8b2e6258e39a?source=cve
Get alerted when CVE-2026-12106 or the next vulnerability affects your stack