CVE-2024-52444
Executive Summary
CVE-2024-52444 is a Path Traversal vulnerability (CWE-22) affecting the WordPress plugin Opal Woo Custom Product Variation (opal-woo-custom-product-variation) versions through 1.1.3. This vulnerability allows an unauthenticated attacker to read arbitrary files on the server by manipulating file paths, potentially exposing sensitive configuration files, database credentials, or source code. The CVSS score is 7.5 (High), with a vector of AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, indicating network-based exploitation with no privileges required. No public proof-of-concept (PoC) or patch is currently available, and the EPSS score is 0.0%, suggesting low exploitation activity at this time.
This record — and 170,000+ others — are available via the ValtersIT API. One endpoint replaces five: NVD + GitHub CVE + CISA KEV + EPSS + Nuclei + Exploit-DB, unified.
No signup required
Supply Chain & Package Security
This vulnerability resides in a WordPress plugin distributed via the official WordPress plugin repository. Users who installed the plugin from the WordPress dashboard or via direct download are affected. The plugin is not available on NPM, PyPI, Go, or Ruby ecosystems. The lack of a patch from the vendor (Wpopal) means that all installations remain vulnerable until a fix is released or the plugin is removed.
CVSS Breakdown & Threat Level
- CVSS Score: 7.5 (High)
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- Attack Vector: Network (AV:N) – Exploitable remotely.
- Attack Complexity: Low (AC:L) – No special conditions required.
- Privileges Required: None (PR:N) – No authentication needed.
- User Interaction: None (UI:N) – No user action required.
- Scope: Unchanged (S:U) – Vulnerability does not affect other components.
- Confidentiality Impact: High (C:H) – Full file read capability.
- Integrity Impact: None (I:N) – No file modification.
- Availability Impact: None (A:N) – No denial of service.
Threat Level: High. The vulnerability is trivial to exploit and can lead to full disclosure of sensitive server files, including wp-config.php which contains database credentials.
Deep Dive & Mechanics
The vulnerability exists in the opal-woo-custom-product-variation plugin due to improper sanitization of user-supplied input used in file path construction. The plugin likely uses a parameter (e.g., file, path, or template) to include or read files without validating that the path stays within the intended directory. An attacker can inject path traversal sequences such as ../ to navigate to arbitrary directories.
Example vulnerable code pattern (hypothetical):
$file = $_GET['file'];
include(plugin_dir_path(__FILE__) . '/templates/' . $file);
An attacker can request ?file=../../../../wp-config.php to read the WordPress configuration file.
The plugin does not implement a whitelist of allowed files or strip traversal sequences, making it susceptible to directory traversal attacks.
Vulnerable vs. Patched Code
Since no patch is available, the vulnerable code remains in all versions <= 1.1.3. A hypothetical patched version would include input validation:
Vulnerable Code (hypothetical):
$file = $_GET['file'];
$path = plugin_dir_path(__FILE__) . '/templates/' . $file;
if (file_exists($path)) {
include($path);
}
Patched Code (hypothetical):
$allowed_files = ['template1.php', 'template2.php'];
$file = basename($_GET['file']); // Remove path components
if (in_array($file, $allowed_files, true)) {
$path = plugin_dir_path(__FILE__) . '/templates/' . $file;
include($path);
} else {
// Deny access
}
The patched version uses basename() to strip directory traversal and a whitelist to restrict accessible files.
Exploitation & Lab Setup
Red Team (Exploitation)
Prerequisites:
- Target WordPress site with Opal Woo Custom Product Variation plugin <= 1.1.3.
- No authentication required.
Exploit Steps:
- Identify the vulnerable endpoint (e.g.,
/wp-content/plugins/opal-woo-custom-product-variation/). - Send a crafted HTTP request with path traversal payload.
Example Request:
GET /wp-content/plugins/opal-woo-custom-product-variation/templates/../../../../wp-config.php HTTP/1.1
Host: target.com
Curl Command:
curl -v "http://target.com/wp-content/plugins/opal-woo-custom-product-variation/templates/../../../../wp-config.php"
Expected Output: The contents of wp-config.php (database credentials, salts, etc.).
Blue Team (Detection & Defense)
Detection:
- Monitor web server logs for path traversal patterns (e.g.,
../or%2e%2e%2f). - Look for requests to plugin directories with suspicious parameters.
Defense:
- Immediately disable or remove the plugin until a patch is available.
- Implement a Web Application Firewall (WAF) rule to block path traversal attempts.
- Restrict file permissions on sensitive files (e.g.,
wp-config.phpshould be readable only by the web server user).
Indicators of Compromise (IOCs)
- File Paths:
/wp-content/plugins/opal-woo-custom-product-variation/ - URL Patterns: Requests containing
../or%2e%2e%2fin the plugin path. - Log Entries: HTTP 200 responses for requests to
wp-config.phpor other sensitive files via the plugin. - Network Traffic: Outbound connections from the server to attacker-controlled IPs (if data exfiltration occurs).
Detection Engineering
YARA Rule
rule CVE_2024_52444_Path_Traversal {
meta:
description = "Detects path traversal attempts targeting Opal Woo Custom Product Variation plugin"
author = "Valters IT"
date = "2025-04-10"
reference = "CVE-2024-52444"
strings:
$traversal1 = "../"
$traversal2 = "..\\"
$traversal3 = "%2e%2e%2f"
$traversal4 = "%2e%2e%5c"
$plugin_path = "opal-woo-custom-product-variation"
condition:
any of ($traversal*) and $plugin_path
}
Sigma Rule
title: CVE-2024-52444 Path Traversal in Opal Woo Custom Product Variation
id: 8a9b3c2d-1e5f-4a7b-9c8d-0e1f2a3b4c5d
status: experimental
description: Detects HTTP requests with path traversal sequences targeting the vulnerable plugin
author: Valters IT
date: 2025-04-10
logsource:
category: webserver
product: apache
detection:
selection:
cs-uri-query|contains:
- '../'
- '..\\'
- '%2e%2e%2f'
- '%2e%2e%5c'
cs-uri-stem|contains: 'opal-woo-custom-product-variation'
condition: selection
falsepositives:
- Legitimate use of similar patterns in other contexts (rare)
level: high
Suricata Rule
alert http any any -> any any (msg:"CVE-2024-52444 Path Traversal in Opal Woo Custom Product Variation"; flow:to_server,established; content:"opal-woo-custom-product-variation"; http_uri; pcre:"/(\.\.\/|\.\.\\|%2e%2e%2f|%2e%2e%5c)/i"; sid:1000001; rev:1;)
Remediation & Mitigation
Immediate Actions:
- Disable the plugin – Deactivate and delete
opal-woo-custom-product-variationfrom the WordPress admin panel. - Apply WAF rules – Block requests containing path traversal sequences in the plugin directory.
- Audit server logs – Check for signs of exploitation (e.g., access to
wp-config.php).
Long-term Fix:
- The vendor (Wpopal) must release a patched version that validates and sanitizes file paths. Until then, do not use the plugin.
- Consider alternative plugins that provide similar functionality with active security maintenance.
Detection Hardening:
- Enable file integrity monitoring (e.g., OSSEC, Tripwire) to detect unauthorized file reads.
- Implement least privilege for web server user (e.g.,
www-data) to limit exposure.
Valters IT
Securing Digital Frontiers
What is this? Security researchers use these exact search queries on Shodan.io (a search engine for internet-connected devices) to find vulnerable systems globally. You can copy these dorks to see if your organization's IP space is exposed.
💣 PoC CODE AVAILABLE
Exploit code for this CVE is tracked in our database.
Access poc_code via API Pro.