Critical (9.8)

Wordpress RCE Vulnerability (CVE-2026-0926)

CVE-2026-0926

The Prodigy Commerce plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 3.2.9 via the 'parameters[template_name]' parameter. This makes it possible for un...

Affected: WordPress

Overview

A critical security vulnerability has been identified in the Prodigy Commerce plugin for WordPress. This flaw allows an unauthenticated attacker to read sensitive files from the server or execute arbitrary PHP code, potentially leading to a complete compromise of the affected website.

Vulnerability Details

The vulnerability is a Local File Inclusion (LFI) flaw within the plugin. Specifically, it exists in the parameters[template_name] parameter. In all versions up to and including 3.2.9, this parameter does not properly validate user input.

In simple terms, this allows an attacker to manipulate a web request to trick the plugin into loading a malicious file from the server’s own file system, instead of the intended template file. By including a file containing PHP code, the attacker can force the server to execute it.

Potential Impact

The consequences of this vulnerability are severe, earning it a CRITICAL CVSS score of 9.8. A successful attack could lead to:

  • Complete System Compromise: Execution of arbitrary PHP code can give an attacker full control over the WordPress site.
  • Data Theft: Attackers can read sensitive files, such as wp-config.php, which contains database credentials and encryption keys.
  • Privilege Escalation: This flaw can be used to bypass normal access controls.
  • Website Defacement or Malware Injection: Attackers can alter site content or install backdoors for persistent access.

Remediation and Mitigation

Immediate action is required to secure affected websites.

Primary Solution - Update:

  1. Update the Plugin: The most important step is to update the Prodigy Commerce plugin to the latest available version immediately. The plugin developers have released a fix in a version higher than 3.2.9.
  2. Verify Update: Log into your WordPress admin panel, navigate to “Plugins,” and check that Prodigy Commerce is updated to a version beyond 3.2.9.

Immediate Mitigation (If Update is Not Instantly Possible):

  • Deactivate the Plugin: If you cannot update immediately, deactivate the Prodigy Commerce plugin via the WordPress admin dashboard. This will close the vulnerability until a secure update can be applied.
  • Consider a Temporary Replacement: Evaluate if an alternative e-commerce solution is needed during the patching process.

General Security Best Practice:

  • Maintain Regular Updates: Always keep all WordPress plugins, themes, and the core installation updated to their latest secure versions.
  • Implement a Web Application Firewall (WAF): A properly configured WAF may help block exploitation attempts targeting this LFI vulnerability.
Share:

Never miss a critical vulnerability

Get real-time security alerts delivered to your preferred platform.

Related Advisories

Other WordPress Vulnerabilities

View all WordPress vulnerabilities →

Never Miss a Critical Alert

CVE advisories, breach reports, and threat intel — delivered daily to your inbox.