Secuno
ENNL
Book demo

CVE-2026-16618

Improve SEO WordPress plugin remote code execution

9.8 CRITICALEPSS 0.83%
  1. Published4 Aug 2026

Description

The Improve SEO WordPress plugin through 2.0.11 does not properly validate uploaded files, checking only the file content type while writing the file with the attacker-supplied extension into a publicly accessible directory, allowing unauthenticated users to upload executable PHP files and achieve remote code execution.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-1040289.8
The Anton Extensions WordPress plugin through 1.2.2 does not perform any capability…
CVE-2026-621299.9
Contributor Arbitrary File Upload in Creator LMS <= 1.2.21…
CVE-2026-620259.0
Unauthenticated Arbitrary File Upload in Tailored Tools <= 3.0.3…
CVE-2026-620249.9
Subscriber Arbitrary File Upload in CodeBard Help Desk <= 1.1.2…
CVE-2026-835268.8
The FV Player 8 plugin for WordPress is vulnerable to Arbitrary File Upload in all…
CVE-2026-1038899.8
The 3D Product configurator for WooCommerce plugin for WordPress is vulnerable to…

Frequently asked

Is CVE-2026-16618 being actively exploited?

CVE-2026-16618 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.83%.

How severe is CVE-2026-16618?

CVE-2026-16618 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.83% probability of exploitation.

How do I fix CVE-2026-16618?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-16618 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.