dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-1404

MEDIUM · 5.3 CVSS v3.1 Published 2025-03-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The WordPress plugin Secure Copy Content Protection and Content Locking has a broken access control vulnerability in the ays_sccp_reports_user_search() function. This function, intended for admin use to search users, lacks a capability check, allowing any unauthenticated visitor to query and retrieve a list of registered user email addresses.

MitigationUpdate the plugin to version 4.4.8 or later which includes proper capability verification on the affected function. Until then, consider restricting access to the affected endpoint via web server configuration or WordPress firewall rules.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm plugin installation
    Log in to WordPress admin and navigate to Plugins > Installed Plugins. Look for 'Secure Copy Content Protection and Content Locking' in the list of active plugins.
    Affected if The plugin is installed and active.
  2. Identify installed version
    In the WordPress admin Plugins page, locate the plugin and view the version number displayed beneath the plugin name. Alternatively, check the plugin's main PHP file (typically named 'secure-copy-content-protection.php' in wp-content/plugins/) for the version header comment.
    Affected if The installed version is lower than 4.4.8.
  3. Test unauthenticated endpoint access
    Send a GET or POST request to the WordPress AJAX endpoint (typically /wp-admin/admin-ajax.php?action=ays_sccp_reports_user_search) without providing any authentication credentials. Use a tool like curl or Burp Suite to observe the response.
    Affected if The endpoint returns user email addresses or valid user data without requiring login.
  4. Inspect the function code
    Locate the file containing ays_sccp_reports_user_search() function within the plugin directory. Examine the function for the presence of a capability check (such as current_user_can() or wp_verify_nonce()) at the function's entry point.
    Affected if No capability check (current_user_can) is present before the user query logic.

You are affected if the plugin is installed with a version below 4.4.8 and the user search endpoint responds to unauthenticated requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 4.4.8 or later which includes proper capability verification on the affected function. Until then, consider restricting access to the affected endpoint via web server configuration or WordPress firewall rules.

Recommended fix High confidence

Plugin version 4.4.8 or later

  1. Check the current version of the 'Secure Copy Content Protection and Content Locking' plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. If the plugin version is 4.4.7 or earlier, update to the latest available version
  4. Verify the update completed successfully and check that the new version is 4.4.8 or later

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1404 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-1404 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data