CVE-2024-6687

CTT Expresso para WooCommerce <= 3.2.12 - Information Exposure via Unprotected Directory

Strategic Overview

Status
Patched in 3.2.13
Affected Version
<= 3.2.12
CVSS
5.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2024-6687
View all CTT Expresso para WooCommerce vulnerabilities

At a glance

CVE-2024-6687 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the CTT Expresso para WooCommerce WordPress plugin, affecting versions <= 3.2.12. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.2.13; sites on affected versions should update now. Disclosed July 2024, reported by Ricardo Silva (Thrill-sea-ker).

Vulnerability Overview

The CTT Expresso para WooCommerce plugin for WordPress is vulnerable to sensitive information exposure in all versions up to and including 3.2.12 via the /wp-content/uploads/cepw directory. The generated .pdf and log files are publicly accessible and contain sensitive information such as sender and receiver names, phone numbers, physical addresses, and email addresses

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in CTT Expresso para WooCommerce <= 3.2.12 takes a caller who can reach the endpoint. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For CTT Expresso para WooCommerce the fix is 3.2.13: builds <= 3.2.12 are affected, anything from 3.2.13 onward is not.

Remediation

Update to version 3.2.13, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: CTT Expresso para WooCommerce 3.2.13 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C