Security readout for executives and security teams
Plain-English summary
Affected WordPress sites may let anyone upload arbitrary files without signing in. If the server accepts and executes a malicious uploaded file, attackers could potentially take complete control of the site, alter content, steal data, or disrupt service.
Executive priority
Treat as an immediate remediation priority for internet-facing sites. Inventory affected installations, contain exposure, and apply vendor-confirmed remediation promptly. Because compromise could affect confidentiality, integrity, and availability, investigate exposed systems for suspicious uploads or endpoint activity rather than assuming an update alone resolves prior intrusion.
Technical view
WPLP Cookie Consent through version 4.4.1 has missing file-type validation in saas_upload_logo(), combined with an authorization bypass affecting connector REST endpoints. The unauthenticated, network-accessible flaw can permit arbitrary server-side file uploads and may enable remote code execution. It is classified as CWE-434 with CVSS 3.1 score 9.8.
Likely exposure
Internet-facing WordPress installations running WPLP Cookie Consent 4.4.1 or earlier are potentially exposed, particularly where the connector REST endpoint is reachable. The supplied affected-version metadata is internally inconsistent, but the title and description consistently specify versions through 4.4.1.
Exploitation context
No active exploitation is established by the supplied sources, and the CVE is not identified as being in CISA KEV. Nevertheless, exploitation requires no authentication or user interaction and has low stated complexity. Successful file upload may lead to remote code execution, depending on server handling and upload location.
Researcher notes
The reported weakness chains authorization bypass with inadequate upload validation. Evidence supports arbitrary unauthenticated file upload; remote code execution is possible, not guaranteed. Execution depends on file placement and web-server behavior. The supplied WordPress changeset is relevant, but the bundle does not explicitly name a fixed release or document exploitation in the wild.
Mitigation direction
- Identify every WordPress site running WPLP Cookie Consent 4.4.1 or earlier.
- Obtain and apply a vendor-confirmed release that addresses the vulnerability.
- Disable or remove the plugin until remediation if a confirmed safe release is unavailable.
- Restrict access to affected connector REST endpoints where operationally feasible.
- Follow Wordfence and WordPress plugin guidance for updated remediation information.
Validation and detection
- Confirm the installed plugin version across production, staging, and dormant WordPress sites.
- Determine whether the WPLP connector REST endpoints are externally reachable without authentication.
- Review web and security logs for suspicious unauthenticated requests to the upload-logo endpoint.
- Inspect upload locations for unexpected files, especially executable or recently created content.
- After remediation, verify unauthorized uploads are rejected and expected consent functions still work.
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 lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. 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-75865 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.9WordfenceVulnerability 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.
- Source timelineWordfence
Discovered
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- Source timelineWordfence
Disclosed
- 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://www.wordfence.com/threat-intel/vulnerabilities/id/96a2a552-e73f-4b27-88de-50eb63a8d131?source=cveCVE reference, Wordfence
- https://plugins.trac.wordpress.org/changeset/3674117/gdpr-cookie-consentCVE reference, Wordfence
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.