Security readout for executives and security teams
Plain-English summary
An internet attacker could upload a malicious PHP file through vulnerable Improve SEO installations without logging in. Because the file is stored in a public location with its attacker-chosen extension, it may execute on the server, enabling website takeover, data theft, tampering, or service disruption.
Executive priority
Treat as an urgent internet-facing exposure. Identify affected sites immediately, disable or isolate the plugin where found, and investigate for suspicious uploads. The potential impact is complete site or server-process compromise, although active exploitation is not established by the supplied sources.
Technical view
Improve SEO through version 2.0.11 reportedly validates only the uploaded content type and preserves the attacker-supplied file extension. An unauthenticated attacker can therefore place executable PHP in a publicly accessible directory. The CVSS 3.1 score is 9.8, reflecting network reachability, low complexity, no privileges, no user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Internet-facing WordPress sites running Improve SEO through 2.0.11 are the likely exposure. Actual risk depends on whether the vulnerable upload functionality is reachable and whether the destination directory executes PHP. The bundle’s structured affected-version entry is incomplete, so confirm scope against current vendor or WPScan guidance.
Exploitation context
The bundle identifies an unauthenticated remote-code-execution path and links a WPScan reference tagged for exploit information. However, it provides no evidence of exploitation in the wild, and the CVE is not listed as KEV. Public exploit maturity cannot be confirmed from the supplied material alone.
Researcher notes
The described weakness maps to CWE-434. Key validation points are authentication requirements, extension handling, storage path accessibility, and server-side PHP execution. The sources do not identify a patched release, vendor identity, exploitation telemetry, or confirmed indicators of compromise. Avoid treating the WPScan exploit tag as proof of active attacks.
Mitigation direction
- Inventory WordPress sites for Improve SEO and record installed versions.
- Disable or remove affected versions until authoritative vendor remediation guidance is available.
- Restrict public access to the vulnerable upload functionality where operationally feasible.
- Prevent PHP execution within directories receiving uploaded files.
- Monitor vendor and WPScan guidance for a confirmed fixed version.
Validation and detection
- Confirm whether Improve SEO is installed and whether its version is 2.0.11 or earlier.
- Verify whether the plugin’s upload functionality is reachable without authentication.
- Inspect public upload directories for unexpected PHP or other executable files.
- Review web and upload logs for unusual unauthenticated requests or file creation.
- Confirm uploaded content cannot execute as server-side code.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-434: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-16618 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://wpscan.com/vulnerability/3754d4c0-1b67-49a4-a29a-7169446638d1/CVE reference, WPScan · exploit, vdb-entry
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Unrestricted Upload of File with Dangerous Type
Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.