← WordPress Vulnerabilities
WordPress security by component

Slim SEO – A Fast & Automated SEO Plugin For WordPress

Slim SEO – A Fast & Automated SEO Plugin For WordPress is a WordPress component with 4 published CVE records in this archive. The latest tracked vulnerability was published Jul 01, 2026; the highest CVE/CNA score is 7.6.

Plugin slug: slim-seo

CVE-2026-12408: Slim SEO – A Fast & Automated SEO Plugin For WordPress: A security weakness

Slim SEO – A Fast & Automated SEO Plugin For WordPress is affected by a security weakness. Exploitation requires at least contributor-level access. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is <= 4.9.8.

PublishedJul 01, 2026
Known safe version> 4.9.8
Safe version
Jul 01, 2026 CVE-2026-12408
Slim SEO – A Fast & Automated SEO Plugin For WordPress: A security weakness
Slim SEO – A Fast & Automated SEO Plugin For WordPress is affected by a security weakness. Exploitation requires at least contributor-level access. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is <= 4.9.8.
> 4.9.8
CVE4.3
NVDPending
Jun 25, 2026 CVE-2026-57429
Slim SEO: A security weakness
Slim SEO is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is n/a through 4.6.2.
4.7.0
CVE6.5
NVDPending
Jun 17, 2025 CVE-2025-49854
Slim SEO: SQL injection
Slim SEO is affected by SQL injection. Exposure depends on how the affected operation is made reachable by the site. A successful request can alter database queries and expose or modify WordPress data.
See mitigation notes
CVE7.6
NVDPending
May 21, 2025 CVE-2025-4611
Slim SEO – Fast & Automated WordPress SEO Plugin: Cross-site scripting
Slim SEO – Fast & Automated WordPress SEO Plugin is affected by cross-site scripting. Exploitation requires at least contributor-level access. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE6.4
NVDPending