CVE-2026-0926 — AI Deep Analysis Summary

Q: Root Cause? (CWE/Flaw)

🛡️ **CWE-98**: Improper Control of Filename for Include/Require. 🔍 **Flaw**: The `parameters[template_name]` parameter lacks proper sanitization, allowing path traversal.

Q: Who is affected? (Versions/Components)

📦 **Vendor**: ProdigyCommerce. 📉 **Affected**: WordPress Plugin **Prodigy Commerce** versions **3.2.9 and earlier**. 🌐 **Platform**: WordPress sites using this plugin.

Q: What can hackers do? (Privileges/Data)

🕵️ **Privileges**: Unauthenticated access required. 📂 **Data**: Can include/read **arbitrary files** (e.g., wp-config.php). 💻 **Action**: Potential Remote Code Execution (RCE) via file inclusion.

Q: Is exploitation threshold high? (Auth/Config)

⚡ **Threshold**: LOW. 🔓 **Auth**: None required (PR:N). 🎯 **Complexity**: Low (AC:L). 🖱️ **User Interaction**: None (UI:N). 📊 **CVSS**: 9.8 (Critical).

Q: Is there a public Exp? (PoC/Wild Exploitation)

📜 **PoC**: Yes. 🔗 **Source**: Nuclei templates available on GitHub (ProjectDiscovery). 🌍 **Exploitation**: Remote exploitation is possible via the specific parameter.

Q: How to self-check? (Features/Scanning)

🔍 **Check**: Scan for Prodigy Commerce plugin version. 🧪 **Test**: Use Nuclei template `CVE-2026-0926.yaml`. 👀 **Manual**: Inspect `parameters[template_name]` input for LFI behavior.

Q: Is it fixed officially? (Patch/Mitigation)

🛠️ **Fix**: Update to version **> 3.2.9**. 📝 **Reference**: Changeset 3464655 in WordPress Trac. ✅ **Status**: Patch available for the vulnerable component.

Q: What if no patch? (Workaround)

🚧 **Workaround**: Disable the plugin if not in use. 🛡️ **WAF**: Block requests containing `parameters[template_name]` with path traversal characters. 🔒 **Access Control**: Restrict plugin admin endpoints.

Q: Is it urgent? (Priority Suggestion)

🔥 **Priority**: CRITICAL. ⏱️ **Urgency**: Immediate action required. 📉 **Risk**: High CVSS score (9.8) + Unauthenticated + RCE potential. Patch ASAP!

Updated May 06, 2026 CVSS 9.8 · Critical

This is a summary of the AI-generated 10-question deep analysis. The full version (longer answers, follow-up Q&A, related CVEs) requires login. Read the full analysis →

Q1What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: Local File Inclusion (LFI) in Prodigy Commerce plugin. <br>💥 **Consequences**: Attackers can read arbitrary files or execute code on the server.…

Read full answer (login)

Q2Root Cause? (CWE/Flaw)

🛡️ **CWE-98**: Improper Control of Filename for Include/Require. <br>🔍 **Flaw**: The `parameters[template_name]` parameter lacks proper sanitization, allowing path traversal.

Q3Who is affected? (Versions/Components)

📦 **Vendor**: ProdigyCommerce. <br>📉 **Affected**: WordPress Plugin **Prodigy Commerce** versions **3.2.9 and earlier**. <br>🌐 **Platform**: WordPress sites using this plugin.

Q4What can hackers do? (Privileges/Data)

🕵️ **Privileges**: Unauthenticated access required. <br>📂 **Data**: Can include/read **arbitrary files** (e.g., wp-config.php). <br>💻 **Action**: Potential Remote Code Execution (RCE) via file inclusion.

Q5Is exploitation threshold high? (Auth/Config)

⚡ **Threshold**: LOW. <br>🔓 **Auth**: None required (PR:N). <br>🎯 **Complexity**: Low (AC:L). <br>🖱️ **User Interaction**: None (UI:N). <br>📊 **CVSS**: 9.8 (Critical).

Q6Is there a public Exp? (PoC/Wild Exploitation)

📜 **PoC**: Yes. <br>🔗 **Source**: Nuclei templates available on GitHub (ProjectDiscovery). <br>🌍 **Exploitation**: Remote exploitation is possible via the specific parameter.

Q7How to self-check? (Features/Scanning)

🔍 **Check**: Scan for Prodigy Commerce plugin version. <br>🧪 **Test**: Use Nuclei template `CVE-2026-0926.yaml`. <br>👀 **Manual**: Inspect `parameters[template_name]` input for LFI behavior.

Q8Is it fixed officially? (Patch/Mitigation)

🛠️ **Fix**: Update to version **> 3.2.9**. <br>📝 **Reference**: Changeset 3464655 in WordPress Trac. <br>✅ **Status**: Patch available for the vulnerable component.

Q9What if no patch? (Workaround)

🚧 **Workaround**: Disable the plugin if not in use. <br>🛡️ **WAF**: Block requests containing `parameters[template_name]` with path traversal characters. <br>🔒 **Access Control**: Restrict plugin admin endpoints.

Q10Is it urgent? (Priority Suggestion)

🔥 **Priority**: CRITICAL. <br>⏱️ **Urgency**: Immediate action required. <br>📉 **Risk**: High CVSS score (9.8) + Unauthenticated + RCE potential. Patch ASAP!

Continue exploring

Vulnerability detail Full AI analysis (login) prodigycommerce CWE-98