Automatic
wp-automatic · plugin
Known security vulnerabilities for Automatic. Find out in seconds which version runs on your site with WP Lens.
5 known vulnerabilities
2 critical · 5 exploitable without logging in · 2 with public exploit code · latest Jun 26, 2026
Not in the wordpress.org directory (paid or third-party distribution). We cannot verify its latest release or maintenance status here; fixed-version data comes from the record itself.
wordpress.org status checked on Oct 2, 2026
Vulnerabilities
- Critical 9.8
CVE-2024-27956unauthenticated≤ 3.92.0
WordPress Automatic plugin <= 3.92.0 - Unauthenticated Arbitrary SQL Execution vulnerability
- Critical 9.3
CVE-2024-27954unauthenticated≤ 3.92.0
WordPress Automatic plugin <= 3.92.0 - Unauthenticated Arbitrary File Download and SSRF vulnerability
- High 8.8
CVE-2024-27955unauthenticated · needs a click≤ 3.92.0
WordPress Automatic plugin <= 3.92.0 - CSRF to Privilege Escalation vulnerability
- High 7.6
CVE-2024-32693unauthenticated · needs a click→ 3.93.0
WordPress Automatic plugin < 3.93.0 - Multiple Cross Site Request Forgery (CSRF) vulnerability
- High 7.1
CVE-2026-56045unauthenticated · needs a click→ 3.135.1
WordPress Automatic plugin < 3.135.1 - Cross Site Scripting (XSS) vulnerability
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).