Skip to main content

CVE-2025-9215: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in kodezen StoreEngine – Powerful WordPress eCommerce Plugin for Payments, Memberships, Affiliates, Sales & More

Medium
VulnerabilityCVE-2025-9215cvecve-2025-9215cwe-22
Published: Wed Sep 17 2025 (09/17/2025, 06:17:47 UTC)
Source: CVE Database V5
Vendor/Project: kodezen
Product: StoreEngine – Powerful WordPress eCommerce Plugin for Payments, Memberships, Affiliates, Sales & More

Description

The StoreEngine – Powerful WordPress eCommerce Plugin for Payments, Memberships, Affiliates, Sales & More plugin for WordPress is vulnerable to Path Traversal in all versions up to, and including, 1.5.0 via the file_download() function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to read the contents of arbitrary files on the server, which can contain sensitive information.

AI-Powered Analysis

AILast updated: 09/17/2025, 13:00:09 UTC

Technical Analysis

CVE-2025-9215 is a path traversal vulnerability (CWE-22) found in the StoreEngine WordPress plugin developed by kodezen, which is used for eCommerce functionalities including payments, memberships, affiliates, and sales. The vulnerability affects all versions up to and including 1.5.0. It arises from improper validation and limitation of file paths in the file_download() function, allowing an authenticated user with at least Subscriber-level privileges to manipulate the file path parameter to access arbitrary files on the server. This can lead to unauthorized disclosure of sensitive information stored on the server, such as configuration files, database credentials, or other private data. The vulnerability does not require user interaction beyond authentication and can be exploited remotely over the network. The CVSS v3.1 base score is 6.5 (medium severity), reflecting high confidentiality impact but no impact on integrity or availability. The attack vector is network-based with low attack complexity, requiring privileges but no user interaction. No known exploits are currently reported in the wild, and no official patches have been linked yet. The vulnerability is significant because WordPress is widely used, and eCommerce plugins often handle sensitive customer and payment data, increasing the risk if exploited.

Potential Impact

For European organizations, this vulnerability poses a risk of sensitive data exposure, including customer personal information, payment details, and internal configuration files. Such data breaches can lead to regulatory non-compliance under GDPR, resulting in heavy fines and reputational damage. The ability for low-privilege authenticated users to access arbitrary files increases the attack surface, especially in environments where subscriber or low-level accounts are easily created or compromised. This could facilitate further attacks such as privilege escalation or lateral movement within the network. The exposure of payment-related data is particularly critical for eCommerce businesses, potentially leading to financial fraud or identity theft. Additionally, the breach of internal files could reveal credentials or system details that attackers can leverage for more extensive intrusions. The medium severity score indicates a significant but not immediately catastrophic risk, emphasizing the need for timely mitigation to prevent exploitation.

Mitigation Recommendations

European organizations using the StoreEngine plugin should immediately audit their WordPress installations to identify affected versions (up to 1.5.0). Until an official patch is released, they should implement strict access controls to limit Subscriber-level account creation and monitor for suspicious file access patterns. Employing Web Application Firewalls (WAFs) with custom rules to detect and block path traversal attempts targeting the file_download() function can reduce risk. Additionally, organizations should review and harden file permissions on the server to restrict access to sensitive files, ensuring that the web server user has minimal privileges. Regularly scanning logs for anomalous access to files outside expected directories can help detect exploitation attempts early. Organizations should also prepare to apply patches promptly once available and consider isolating the WordPress environment or using containerization to limit potential damage. Finally, educating users about the risks of account compromise and enforcing strong authentication mechanisms can reduce the likelihood of attacker footholds.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-08-19T20:03:22.388Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68cab09db62c8e2e63b2468e

Added to database: 9/17/2025, 12:59:09 PM

Last enriched: 9/17/2025, 1:00:09 PM

Last updated: 9/17/2025, 3:07:09 PM

Views: 3

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats