Security readout for executives and security teams
Plain-English summary
Media Library Assistant versions through 3.39 reportedly allow a WordPress Author to upload arbitrary files. If abused, this could compromise site confidentiality, content integrity, and availability. The supplied evidence does not identify a fixed release or confirm attacks in the wild.
Executive priority
Treat this as an urgent validation and remediation task for affected WordPress sites. The potential impact is critical, but exploitation requires authentication and active attacks are not confirmed. Establish exposure promptly, reduce privileged account risk, and follow verified vendor guidance before declaring remediation complete.
Technical view
CVE-2026-66600 is classified as CWE-434 with CVSS 3.1 score 9.1 (AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H). The issue is remotely reachable, requires authenticated privileges, needs no user interaction, and may affect resources beyond the vulnerable component. Endpoint and file-handling details are not provided.
Likely exposure
Prioritize WordPress sites running the Media Library Assistant plugin at version 3.39 or earlier, particularly where Author-capable accounts exist. The bundle’s structured affected-version field says “n/a” and defaults to unaffected, conflicting with the title and description; confirm scope with vendor guidance.
Exploitation context
The supplied bundle marks this CVE as absent from KEV, and no cited source in the bundle claims active exploitation. Exploitation requires an authenticated account according to the description and CVSS vector. Public exploit availability and observed attack activity are not established by the evidence provided.
Researcher notes
The record provides only a concise Author arbitrary-file-upload description, CWE-434, and CVSS metadata. It does not specify the vulnerable endpoint, accepted file types, upload destination, execution conditions, fixed version, proof of exploitation, or vendor mitigation. The affected metadata conflicts with the stated through-3.39 scope.
Mitigation direction
- Inventory Media Library Assistant installations and identify versions 3.39 or earlier.
- Check vendor and Patchstack guidance for a confirmed fixed release or official mitigation.
- Restrict or remove unnecessary Author-level accounts and review their access.
- Disable the plugin temporarily where exposure is unacceptable and no confirmed fix is available.
- Maintain tested backups and apply normal WordPress file-execution protections.
Validation and detection
- Confirm the installed plugin version on every WordPress site.
- Review Author-capable accounts for legitimacy, recent creation, or compromise indicators.
- Inspect media uploads and related logs for unexpected files or upload activity.
- Verify any updated version against current vendor or Patchstack guidance.
- Monitor CVE and KEV records for revised scope or exploitation evidence.
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 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-66600 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.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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:H/UI:N/S:C/C:H/I:H/A:H2.36PatchstackVulnerability scoring details
Base CVSS 3.1 score
9.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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
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.