Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-13638: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor in sldesignpl Order Attachments for WooCommerce

0
Medium
VulnerabilityCVE-2024-13638cvecve-2024-13638cwe-200
Published: Fri Feb 28 2025 (02/28/2025, 08:23:17 UTC)
Source: CVE Database V5
Vendor/Project: sldesignpl
Product: Order Attachments for WooCommerce

Description

CVE-2024-13638 is a medium severity vulnerability in the Order Attachments for WooCommerce WordPress plugin (all versions up to 2. 5. 1). It allows unauthenticated attackers to access sensitive files stored insecurely in the /wp-content/uploads directory, exposing order-related attachments. Exploitation requires no authentication or user interaction but has a high attack complexity due to the need to locate specific files. The vulnerability impacts confidentiality but not integrity or availability. No known exploits are currently reported in the wild. Organizations using this plugin should restrict direct access to uploaded files and monitor for unauthorized access attempts.

AI-Powered Analysis

AILast updated: 02/25/2026, 23:16:29 UTC

Technical Analysis

The vulnerability identified as CVE-2024-13638 affects the Order Attachments for WooCommerce plugin developed by sldesignpl, which is widely used in WordPress e-commerce sites to manage file attachments related to customer orders. The issue arises because the plugin stores sensitive order-related attachments in the standard WordPress uploads directory (/wp-content/uploads) without adequate access controls or protections. This misconfiguration allows unauthenticated attackers to directly access these files via HTTP requests, leading to exposure of potentially sensitive information such as customer documents, invoices, or other private data attached to orders. The CVSS 3.1 score of 5.9 reflects a medium severity level, with an attack vector of network (AV:N), high attack complexity (AC:H), no privileges required (PR:N), no user interaction (UI:N), unchanged scope (S:U), high confidentiality impact (C:H), and no impact on integrity or availability (I:N/A:N). The high attack complexity suggests that while no authentication is needed, attackers must identify or guess the exact file paths or names to exploit the vulnerability. No patches or fixes are currently linked, and no exploits have been reported in the wild, indicating this is a newly disclosed issue. The root cause is a CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), highlighting improper access control on sensitive files. This vulnerability underscores the importance of securing file storage and access permissions in WordPress plugins handling sensitive customer data.

Potential Impact

The primary impact of CVE-2024-13638 is the unauthorized disclosure of sensitive customer information stored as order attachments, which can include personal documents, invoices, or other confidential files. This exposure can lead to privacy violations, regulatory non-compliance (e.g., GDPR, CCPA), reputational damage, and potential legal consequences for affected organizations. Since the vulnerability does not affect data integrity or system availability, the risk is confined to confidentiality breaches. However, the ease of access without authentication increases the threat level, especially for e-commerce sites handling sensitive customer data. Attackers could use the exposed information for identity theft, fraud, or targeted phishing attacks. Organizations relying on this plugin may face customer trust erosion and financial penalties if sensitive data is leaked. The lack of known exploits in the wild currently limits immediate widespread impact, but the vulnerability’s public disclosure may prompt attackers to develop exploitation techniques.

Mitigation Recommendations

To mitigate CVE-2024-13638, organizations should immediately implement strict access controls on the /wp-content/uploads directory to prevent direct public access to sensitive order attachments. This can be achieved by configuring web server rules (e.g., .htaccess for Apache or location blocks for Nginx) to restrict access to authorized users or to deny access to specific file types or directories used by the plugin. Additionally, plugin users should monitor for updates or patches from the vendor and apply them promptly once available. As a temporary measure, consider moving sensitive attachments outside the web root or using secure storage solutions with authentication controls. Regularly audit uploaded files for sensitive content and review access logs for suspicious activity. Employing a Web Application Firewall (WAF) with rules to block unauthorized access attempts to upload directories can further reduce risk. Finally, educate site administrators on secure plugin configuration and the risks of exposing sensitive files via public directories.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-01-22T22:31:56.749Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6e64b7ef31ef0b59fce7

Added to database: 2/25/2026, 9:49:24 PM

Last enriched: 2/25/2026, 11:16:29 PM

Last updated: 2/26/2026, 6:54:40 AM

Views: 1

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

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

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats