Security readout for executives and security teams
Plain-English summary
GP Premium for WordPress through version 2.5.5 reportedly allows a logged-in, low-privileged attacker to upload a dangerous file. Successful abuse could let attacker-controlled code run on the website, potentially exposing data, changing content, disrupting service, or enabling broader compromise.
Executive priority
Urgent. Identify affected sites immediately and reduce exposure, prioritizing public or business-critical WordPress systems. Because successful exploitation could enable full site compromise and no confirmed fixed version appears in the bundle, require explicit verification of vendor guidance and evidence-based compromise review.
Technical view
This is CWE-434 unrestricted file upload leading to remote code inclusion. CVSS 3.1 rates it 9.9: network-accessible, low complexity, low privileges required, no user interaction, changed scope, and high confidentiality, integrity, and availability impact. The supplied sources do not identify the vulnerable endpoint, minimum required role, fixed release, or technical mitigation.
Likely exposure
Likely exposure is limited to WordPress installations running GP Premium version 2.5.5 or earlier where an attacker can obtain the required low-privileged account. The supplied metadata does not establish the earliest affected version, exact permissions required, configuration dependencies, or internet-wide deployment prevalence.
Exploitation context
The CVSS vector indicates authenticated remote exploitation with low complexity and no victim interaction. However, GP Premium is not listed as a CISA KEV in the supplied bundle, and no provided source confirms public exploitation, exploit availability, or active attacks. Treat compromise as plausible, not confirmed in the wild.
Researcher notes
The record asserts GP Premium through 2.5.5 is affected, but its structured affected entry contains version “n/a” with default status “unaffected.” This inconsistency, plus absent endpoint, authorization-role, patch, and exploitation details, limits precision. Validate against updated CVE and Patchstack records before making version-specific closure decisions.
Mitigation direction
- Inventory WordPress sites and identify GP Premium installations at version 2.5.5 or earlier.
- Check vendor and Patchstack guidance for a confirmed corrected release; the supplied sources name none.
- Disable or remove affected installations until a verified fix is available, where operationally feasible.
- Restrict unnecessary WordPress accounts and revoke unneeded low-privilege access.
- Apply defense-in-depth controls preventing uploaded files from executing as server-side code.
Validation and detection
- Confirm the installed GP Premium version on every WordPress instance.
- Review privileged and low-privileged accounts for unknown, stale, or compromised access.
- Inspect recent files and upload locations for unexpected executable or obfuscated content.
- Review web, authentication, and security logs for suspicious authenticated upload activity.
- After remediation, verify the plugin is removed, disabled, or on a vendor-confirmed safe version.
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-66627 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.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/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:L/UI:N/S:C/C:H/I:H/A:H3.16PatchstackVulnerability scoring details
Base CVSS 3.1 score
9.9CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/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
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/wordpress/plugin/gp-premium/vulnerability/wordpress-gp-premium-plugin-2-5-5-arbitrary-file-upload-vulnerability?_s_id=cveCVE reference, Patchstack · 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.