# CVE-2025-1404: Missing authorization in Secure Copy Content Protection and Content Locking

> Unauthenticated attackers can retrieve registered user emails due to a missing capability check in the Secure Copy Content Protection plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Mar 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-8jxw-vxhj-q8p7

## What is CVE-2025-1404?

CVE-2025-1404 is a medium-severity missing authorization vulnerability in ays-pro Secure Copy Content Protection and Content Locking, published on 1 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2025-1404?


## How do I fix CVE-2025-1404?

No fix has been published for CVE-2025-1404 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-1404 being exploited?

There is no known exploitation of CVE-2025-1404 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-1404 and fix it if it is affected.

What it is: CVE-2025-1404 is a medium-severity missing authorization vulnerability in ays-pro Secure Copy Content Protection and Content Locking, published on 1 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-1404 in the wild and no public exploit code.

Affected product: ays-pro Secure Copy Content Protection and Content Locking. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-1404/ (Markdown: https://insights.sbomify.com/CVE-2025-1404/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-1404
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-1404
- OSV: https://osv.dev/vulnerability/CVE-2025-1404

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-1404/
Summaries are generated and may contain mistakes; the official description above is the record.