Security readout for executives and security teams
Plain-English summary
A public website running Gift Cards For WooCommerce Pro before 4.2.10 could let anyone upload a malicious file without signing in. Because uploaded PHP code may execute on the server, an attacker could steal data, alter the site, install persistent access, or disrupt service.
Executive priority
Prioritize immediate identification and remediation of internet-facing installations. A vulnerable site may permit full server-side code execution without credentials. Escalate any evidence of unexpected executable uploads or unauthorized changes to incident response; patching alone may not remove persistence from an already compromised system.
Technical view
The plugin fails to validate file types in an unauthenticated upload path, creating CWE-434 unrestricted file upload. Network access, low complexity, no privileges, and no user interaction are required. Successful upload of executable PHP can lead to remote code execution with high confidentiality, integrity, and availability impact.
Likely exposure
Internet-accessible WordPress sites using Gift Cards For WooCommerce Pro versions earlier than 4.2.10 are the likely exposure. The bundle’s structured affected-product entry inconsistently identifies “giftware,” version “0,” and default unaffected status, so administrators should verify plugin identity and installed version directly.
Exploitation context
The CVSS 3.1 score is 9.8. The WPScan reference is tagged “exploit,” but the supplied evidence does not establish exploitation in the wild. CVE-2026-15039 is not listed as KEV in the bundle. Treat exposed installations as urgent because exploitation requires no authentication or user interaction.
Researcher notes
The source bundle supports an unauthenticated arbitrary-file-upload condition before 4.2.10 and potential PHP code execution. It does not provide the affected endpoint, product CPE, attack telemetry, or confirmed exploitation. The inconsistent affected-product metadata reduces confidence in automated asset matching; validate against installed plugin metadata and current vendor guidance.
Mitigation direction
- Update Gift Cards For WooCommerce Pro to version 4.2.10 or later after confirming vendor guidance.
- Disable or remove the plugin until updating if its vulnerable upload functionality is publicly reachable.
- Restrict unnecessary access to upload paths using application or edge controls.
- If compromise is suspected, isolate the site and begin incident response before restoring service.
Validation and detection
- Inventory all WordPress sites and confirm the plugin name, installation status, and exact version.
- Verify the deployed version is 4.2.10 or later and the update completed successfully.
- Review upload directories for unexpected PHP files or other executable content.
- Examine web and security logs for suspicious unauthenticated uploads and subsequent access to uploaded files.
- Check WordPress files, accounts, scheduled tasks, and configuration for unauthorized changes.
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-15039 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/b7b3308c-430e-4bc3-a3df-da20d47cf314/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.