CVE-2025-14442

Secure Copy Content Protection and Content Locking <= 4.9.2 - Unauthenticated Sensitive Information Exposure via Exposed CSV Export File

2025-12-11 21:22
Deadbee

Strategic Overview

Status
Patched in 4.9.3
Affected Version
<= 4.9.2
CVSS
5.3Medium
Weakness type
CWE-552 · Files or Directories Accessible to External Parties
CVE
CVE-2025-14442
View all Secure Copy Content Protection and Content Locking vulnerabilities

At a glance

CVE-2025-14442 is a medium-severity Files or Directories Accessible to External Parties vulnerability in the Secure Copy Content Protection and Content Locking WordPress plugin, affecting versions <= 4.9.2. 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 4.9.3; sites on affected versions should update now. Disclosed December 2025, reported by Deadbee.

Vulnerability Overview

The Secure Copy Content Protection and Content Locking plugin for WordPress is vulnerable to sensitive information exposure due to storage of exported CSV files in a publicly accessible directory with predictable filenames in all versions up to, and including, 4.9.2. This makes it possible for unauthenticated attackers to access sensitive user data including emails, IP addresses, usernames, roles, and location data by directly accessing the exported CSV file.

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-552: Files or Directories Accessible to External Parties

The product makes files or directories accessible to unauthorized actors, even though they should not be.

Remediation

Update to version 4.9.3, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Secure Copy Content Protection and Content Locking 4.9.3 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Login Security
  • Alerts

External References

Related records

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