S4E just found a high-severity finding from top 10 tcp port service scan
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
critical·Product Based Web Vulnerabilities·Updated Mar 16, 2026

CVE-2026-0926 Scanner

Targets the 'file' parameter in the download endpoint, allowing attackers to read arbitrary server files.

Est. Time~10 seconds
Scan TypeSingle Scan
Targetsdomain, subdomain, ipv4
CostFree
2k
Times Used
continuous scan runs
4.1k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
CVECVE-2026-0926
9.8
CVSScritical
Exploitable remotely over the internet · no authentication required.

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.

Attack Vector
Network
Privileges Req.
None
User Interaction
None
Affected
Prodigy Commerceby prodigycommerce
0
Updated Aug 22, 2026View on NVD →
Detail

Prodigy Commerce is a WordPress plugin designed for small to medium-sized businesses to create and manage online stores. It simplifies product listings, order management, and payment processing, integrating seamlessly with various themes. Users rely on it for its customizable features and support for multiple payment gateways, making it a popular choice for retailers seeking an easy e-commerce solution without extensive technical knowledge.

Local File Inclusion (LFI) is a vulnerability that occurs when user input is not properly sanitized, allowing attackers to include arbitrary files from the server. In Prodigy Commerce, this arises due to insufficient validation of file paths in certain functions, enabling malicious actors to traverse directories and access sensitive files outside the intended scope.

The vulnerability specifically affects the 'download' endpoint in Prodigy Commerce versions prior to 3.2.9. The 'file' parameter is not sanitized, allowing path traversal sequences like '../' to read files such as '/etc/passwd' or WordPress configuration files. This endpoint is used for downloading invoices or receipts, making it a prime target for exploitation.

If exploited, an attacker can read sensitive server files, including database credentials, API keys, and source code. This can lead to full site compromise, data breaches, and potential remote code execution if combined with other vulnerabilities. The high CVSS score of 9.8 reflects the critical risk to confidentiality, integrity, and availability.

Solution Advice
  • Update Prodigy Commerce to version 3.2.9 or later immediately.
  • Implement strict input validation on the 'file' parameter to allow only expected file names.
  • Use a whitelist approach for file paths rather than blacklisting dangerous characters.
  • Disable PHP functions like file_get_contents() if not required for plugin functionality.
  • Apply a Web Application Firewall (WAF) with rules to block path traversal patterns.
  • Regularly audit and update all WordPress plugins and themes for security patches.
  • Enable detailed logging to monitor and alert on suspicious file inclusion attempts.
  • Restrict file permissions on the server to limit access to sensitive files.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

11,000+ scanners. Free to start. No credit card required.