Skip to content
Fencer Intel
critical 9.8

CVE-2026-0926 json

Prodigy Commerce <= 3.3.0 - Unauthenticated Local File Inclusion via parameters[template_name]

published 8mo ago modified 4mo ago also EUVD-2026-8228

cvss
9.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
9.3%
EPSS 9.3% chance of exploitation in 30 days, percentile 95%
public exploits
1
Exploit-DB, plus a Nuclei check

Summary

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.

Is CVE-2026-0926 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. Published
  2. First public exploit (EDB-52598)

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
8mo ago

Exploit prediction

9.30% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-52598 Prodigy Commerce 3.3.0 - Local File Inclusion webapps, 2026-05-29
  • Nuclei template Prodigy Commerce <= 3.3.0 - Local File Inclusion nuclei detection template

CVSS scores

assigned by version score vector
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

  • prodigycommerce Prodigy Commerce

Classification

Weakness
  • CWE-98 Improper Control of Filename for Include/Require Statement in PHP Program
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.