dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2026-0926

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Prodigy Commerce plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 3.3.0 via the 'parameters[template_name]' parameter. This makes it possible for unauthenticated attackers to include and read arbitrary files or execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Prodigy Commerce WordPress plugin (versions up to 3.3.0) contains a Local File Inclusion vulnerability in the 'parameters[template_name]' parameter. Unauthenticated attackers can include arbitrary files from the server filesystem and execute embedded PHP code, leading to complete system compromise including remote code execution, data exfiltration, and access control bypass.

MitigationUpdate the Prodigy Commerce plugin to a version beyond 3.3.0 when available. If no patched version exists, disable the plugin immediately. Additionally, disable PHP execution in upload directories and review server access logs for signs of exploitation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Prodigy Commerce plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Prodigy Commerce' in the list, or check the filesystem at /wp-content/plugins/ for a prodigy-commerce or similar directory
    Affected if The Prodigy Commerce plugin is found in the WordPress installation
  2. Check installed plugin version
    In WordPress admin Plugins list, click on the Prodigy Commerce plugin to view its details and version number, or inspect the main plugin file header in /wp-content/plugins/ for the 'Version' field
    Affected if The installed version is 3.3.0 or lower (any version up to and including 3.3.0)
  3. Confirm vulnerable parameter exposure
    Identify the plugin's PHP files that handle the 'template_name' parameter, typically in request handlers or template routing code. Search the plugin directory for 'parameters[template_name]' or 'template_name' in $_GET/$_POST request handling code
    Affected if The plugin code processes the template_name parameter without proper sanitization in include/require statements
  4. Review access logs for exploitation attempts
    Examine web server access logs (Apache error.log, access.log or Nginx access.log) for requests containing 'parameters[template_name]' or '../' path traversal sequences targeting the plugin endpoint
    Affected if Logs contain requests to the plugin with path traversal patterns like '../' or references to the template_name parameter

You are affected if the Prodigy Commerce plugin is installed and its version is 3.3.0 or lower, and the vulnerable template_name parameter handling code is present and accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Prodigy Commerce plugin to a version beyond 3.3.0 when available. If no patched version exists, disable the plugin immediately. Additionally, disable PHP execution in upload directories and review server access logs for signs of exploitation.

Recommended fix Moderate confidence

Version newer than 3.3.0 (check WordPress plugin repository for latest release)

  1. Check the WordPress plugin repository for Prodigy Commerce to identify if a version newer than 3.3.0 has been released
  2. If a newer version exists, navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Deactivate the current Prodigy Commerce plugin
  4. Update the plugin to the latest available version
  5. Verify the update was successful by confirming the new version number in the plugins list
  6. Test critical e-commerce functionality to ensure the update did not break existing features

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0926 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-0926 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data