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-2025-1404: CWE-862 Missing Authorization in ays-pro Secure Copy Content Protection and Content Locking

0
Medium
VulnerabilityCVE-2025-1404cvecve-2025-1404cwe-862
Published: Sat Mar 01 2025 (03/01/2025, 11:22:48 UTC)
Source: CVE Database V5
Vendor/Project: ays-pro
Product: Secure Copy Content Protection and Content Locking

Description

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.

AI-Powered Analysis

AILast updated: 02/25/2026, 21:56:46 UTC

Technical Analysis

CVE-2025-1404 is a vulnerability classified under CWE-862 (Missing Authorization) found in the ays-pro Secure Copy Content Protection and Content Locking plugin for WordPress. The issue stems from the absence of a capability check in the function ays_sccp_reports_user_search(), which is responsible for handling user search queries within the plugin. Because this function lacks proper authorization enforcement, unauthenticated attackers can invoke it remotely to retrieve a list of registered user email addresses. This vulnerability affects all versions of the plugin up to and including version 4.4.7. The CVSS 3.1 base score is 5.3, reflecting a medium severity level, with an attack vector of network (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), and impact limited to confidentiality (C:L) without affecting integrity or availability. The vulnerability does not require authentication or user interaction, making it easier to exploit remotely. Although no known exploits are currently reported in the wild, the exposure of user emails can be leveraged for further attacks such as phishing campaigns or credential stuffing. The plugin is used in WordPress environments, which are widely deployed globally, increasing the potential attack surface. No official patches or fixes have been released at the time of publication, so mitigation relies on compensating controls and monitoring.

Potential Impact

The primary impact of CVE-2025-1404 is the unauthorized disclosure of registered user email addresses from websites using the affected plugin. This breach of confidentiality can facilitate targeted phishing, spear-phishing, and social engineering attacks against users, potentially leading to credential compromise or further exploitation. While the vulnerability does not directly affect data integrity or availability, the indirect consequences of leaked emails can be significant, especially for organizations with sensitive or high-profile user bases. Attackers can automate the extraction of email lists without authentication, increasing the scale and speed of data harvesting. Organizations relying on this plugin face reputational damage, increased risk of account takeover, and potential regulatory compliance issues related to data privacy. The absence of patches increases exposure duration, and the widespread use of WordPress amplifies the potential global impact.

Mitigation Recommendations

To mitigate CVE-2025-1404, organizations should immediately restrict access to the vulnerable plugin's functionalities by implementing web application firewall (WAF) rules that block unauthorized requests to the ays_sccp_reports_user_search() endpoint or related AJAX handlers. Administrators should audit and monitor web server logs for unusual or repeated access attempts targeting this function. If possible, disable or uninstall the Secure Copy Content Protection and Content Locking plugin until a vendor patch is available. Employ rate limiting and IP reputation filtering to reduce automated exploitation attempts. Additionally, organizations should educate users about phishing risks and enforce strong authentication mechanisms such as multi-factor authentication (MFA) to mitigate the impact of potential credential compromise. Regularly check for vendor updates or security advisories and apply patches promptly once released. Consider isolating WordPress administrative interfaces behind VPNs or IP allowlists to reduce exposure.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-02-17T20:28:28.345Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6b11b7ef31ef0b54dc34

Added to database: 2/25/2026, 9:35:13 PM

Last enriched: 2/25/2026, 9:56:46 PM

Last updated: 2/26/2026, 8:05:10 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