Security readout for executives and security teams
Plain-English summary
CVE-2026-0926 affects the Prodigy Commerce WordPress plugin through version 3.3.0. An unauthenticated internet user may be able to make the site load unintended local files. In severe cases, this can expose sensitive data or execute PHP already present on the server.
Executive priority
Treat as urgent for any internet-facing commerce site using this plugin. The impact can include customer data exposure, site compromise, and service disruption. Prioritize verification and remediation within the normal emergency patch process.
Technical view
The issue is a Local File Inclusion weakness, CWE-98, in Prodigy Commerce <= 3.3.0 via the parameters[template_name] parameter. The CVSS 3.1 score is 9.8. Public references point to template-handling code paths and a WordPress.org changeset, but the provided sources do not confirm exploitation in the wild.
Likely exposure
Public WordPress sites running Prodigy Commerce version 3.3.0 or earlier are the primary concern, especially if unauthenticated users can reach affected plugin routes or shortcodes.
Exploitation context
The vulnerability is network-accessible, low complexity, requires no authentication, and requires no user interaction. It may allow file disclosure or PHP execution if attacker-controllable or previously uploaded files can be included. KEV status is false in the provided data.
Researcher notes
Sources identify the vulnerable parameter and affected version range, with code references for template inclusion paths. The provided bundle does not include confirmed active exploitation, a KEV listing, or a clearly named fixed version. Avoid assuming exploit availability beyond the published vulnerability description.
Mitigation direction
- Identify all WordPress sites using Prodigy Commerce.
- Prioritize sites running Prodigy Commerce 3.3.0 or earlier.
- Check WordPress.org and vendor guidance for the fixed release or recommended action.
- If no fixed version is available, disable the plugin until guidance is clear.
- Restrict upload capabilities and review server file permissions.
Validation and detection
- Inventory plugin versions across production and staging WordPress sites.
- Confirm whether Prodigy Commerce is active, not merely installed.
- Review web logs for unusual requests containing parameters[template_name].
- Check for unexpected file access errors around plugin template rendering.
- Monitor Wordfence, CVE, and WordPress.org references for updated remediation details.
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-98: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookupCVE-2026-0926 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.
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.9Primary CVE scoreVulnerability 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
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/de255530-6b2d-426b-9f80-dbfebd2e3307?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/prodigy-commerce/trunk/includes/frontend/shortcodes/class-prodigy-short-code-my-account.php#L69CVE reference
- https://plugins.trac.wordpress.org/browser/prodigy-commerce/trunk/includes/frontend/class-prodigy-public.php#L491CVE reference
- https://plugins.trac.wordpress.org/browser/prodigy-commerce/trunk/includes/helpers/class-prodigy-template.php#L55CVE reference
- https://plugins.trac.wordpress.org/browser/prodigy-commerce/tags/3.2.9/includes/helpers/class-prodigy-template.php#L55CVE reference
- https://plugins.trac.wordpress.org/changeset/3464655/CVE reference
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.
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.