# CVE-2025-14442: Information disclosure in Secure Copy Content Protection and Content Locking

> Unauthenticated attackers can access sensitive user data by directly retrieving publicly exposed CSV export files with predictable names.

- **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:** 12 Dec 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-qqj8-52jc-qfhp

## What is CVE-2025-14442?

CVE-2025-14442 is a medium-severity vulnerability in ays-pro Secure Copy Content Protection and Content Locking, published on 12 Dec 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 sensitive information exposure due to storage of exported CSV files in a publicly accessible directory with predictable filenames in all versions up to, and including, 4.9.2. This makes it possible for unauthenticated attackers to access sensitive user data including emails, IP addresses, usernames, roles, and location data by directly accessing the exported CSV file.

Weakness: CWE-552 (Files or Directories Accessible to External Parties)

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


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

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

## Is CVE-2025-14442 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14442 is a medium-severity vulnerability in ays-pro Secure Copy Content Protection and Content Locking, published on 12 Dec 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-14442 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-14442/ (Markdown: https://insights.sbomify.com/CVE-2025-14442/index.md)
```

## Sources

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

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