CVE-2025-1404

Secure Copy Content Protection and Content Locking <= 4.4.7 - Missing Authorization to Unauthenticated User Email Retrieval via ays_sccp_reports_user_search Function

2025-02-28 22:01
Krzysztof Zając

Strategic Overview

Status
Patched in 4.4.8
Affected Plugin
Secure Copy Content Protection and Content Locking
Affected Version
<= 4.4.7
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-1404
View all Secure Copy Content Protection and Content Locking vulnerabilities

At a glance

CVE-2025-1404 is a medium-severity Missing Authorization vulnerability in the Secure Copy Content Protection and Content Locking WordPress plugin, affecting versions <= 4.4.7. 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.4.8; sites on affected versions should update now. Disclosed February 2025, reported by Krzysztof Zając.

Vulnerability Overview

The Secure Copy Content Protection and Content Locking plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the ays_sccp_reports_user_search() function in all versions up to, and including, 4.4.7. This makes it possible for unauthenticated attackers to retrieve a list of registered user emails.

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-862: Missing Authorization

Secure Copy Content Protection and Content Locking <= 4.4.7 carries this weakness at ays_sccp_reports_user_search(), and reaching it takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Secure Copy Content Protection and Content Locking the fix is 4.4.8: builds <= 4.4.7 are affected, anything from 4.4.8 onward is not.

Remediation

Update to version 4.4.8, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Secure Copy Content Protection and Content Locking 4.4.8 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-1404https://www.wordfence.com/threat-intel/vulnerabilities/id/7363b5de-db30-4b35-b701-5c8f2835ec6chttps://nvd.nist.gov/vuln/detail/CVE-2025-1404

Related records

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