CVE-2025-14159

Secure Copy Content Protection and Content Locking <= 4.9.2 - Cross-Site Request Forgery to Data Export

2025-12-11 21:20
Deadbee

Strategic Overview

Status
Patched in 4.9.3
Affected Plugin
Secure Copy Content Protection and Content Locking
Affected Version
<= 4.9.2
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2025-14159
View all Secure Copy Content Protection and Content Locking vulnerabilities

At a glance

CVE-2025-14159 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Secure Copy Content Protection and Content Locking WordPress plugin, affecting versions <= 4.9.2. It carries a CVSS score of 4.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 Cross-Site Request Forgery in all versions up to, and including, 4.9.2. This is due to missing nonce validation on the 'ays_sccp_results_export_file' AJAX action. This makes it possible for unauthenticated attackers to export sensitive plugin data including email addresses, IP addresses, physical addresses, user IDs, and other user information via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. The exported data is stored in a publicly accessible file, allowing attackers to receive the sensitive information even though they are not authenticated.

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.

CWE-352: Cross-Site Request Forgery (CSRF)

Secure Copy Content Protection and Content Locking <= 4.9.2 carries this weakness at ays_sccp_results_export_file, and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Secure Copy Content Protection and Content Locking the fix is 4.9.3: builds <= 4.9.2 are affected, anything from 4.9.3 onward is not.

Remediation

Update to version 4.9.3, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Secure Copy Content Protection and Content Locking: 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
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-14159https://www.wordfence.com/threat-intel/vulnerabilities/id/7cffe04e-a2e5-4752-a5c1-7c95f0007e0bhttps://nvd.nist.gov/vuln/detail/CVE-2025-14159

Related records

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