Security readout for executives and security teams
Plain-English summary
A flaw in the WordPress plugin can let an Editor-level user place executable content in a public server directory. On servers that execute such files, this can enable full remote compromise, including data theft, site modification, and service disruption.
Executive priority
Prioritize immediate exposure assessment. Internet-facing sites with the affected plugin, Editor access risk, and executable upload directories warrant urgent containment. Full remote compromise is possible, although active exploitation is not established by the supplied evidence.
Technical view
The plugin through version 4.3000000027 inadequately validates uploaded archive contents. A bypassable file check permits server-executable file upload into a public directory, creating potential remote code execution when server configuration allows execution there. This is categorized as unrestricted upload of a dangerous file, CWE-434.
Likely exposure
WordPress sites using plugin version 4.3000000027 or earlier may be exposed, particularly where untrusted or compromised users have Editor access and uploaded files can execute. Exposure cannot be determined from version alone because server execution settings affect impact.
Exploitation context
The supplied record is not in CISA KEV and provides no evidence of active exploitation. WPScan is tagged as containing exploit information, but the bundle does not establish observed attacks. Treat exploitation status as unconfirmed.
Researcher notes
The supplied CVSS 3.1 vector states PR:N, while the technical description requires Editor-level access. This material inconsistency affects exploitability assessment and should be verified against the authoritative record. No patched version is identified in the bundle; only versions through 4.3000000027 are stated as affected.
Mitigation direction
- Identify installations and confirm the installed plugin version.
- Check current vendor or WordPress guidance for a fixed release or official mitigation.
- Disable or remove the plugin where operationally acceptable until authoritative remediation is available.
- Restrict Editor access to trusted users and investigate recently changed accounts.
- Prevent executable content from running in public upload directories using supported server controls.
Validation and detection
- Inventory WordPress sites for the plugin and record exact versions.
- Verify whether public upload directories permit server-side file execution.
- Review plugin uploads and public directories for unexpected executable files.
- Audit Editor accounts, recent privilege changes, and suspicious administrative activity.
- After remediation, confirm vulnerable versions are absent or the plugin remains disabled.
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-16060 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/a5937e0d-c1bc-4787-9ab9-ab58b9789b68/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.