# CVE-2025-58670: WordPress WP Content Protection Plugin <= 1.3 - Cross Site Request Forgery (CSRF) Vulnerability

> A CSRF vulnerability in the WP Content Protection plugin allows attackers to inject stored XSS, potentially leading to code execution or data modification.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 22 Sep 2025
- **Updated:** 12 May 2026
- **Also known as:** GHSA-35w5-c9v9-6575

## What is CVE-2025-58670?

CVE-2025-58670 is a high-severity vulnerability in Shankaranand Maurya WP Content Protection, published on 22 Sep 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Cross-Site Request Forgery (CSRF) vulnerability in Shankaranand Maurya WP Content Protection wp-content-protection allows Stored XSS.This issue affects WP Content Protection: from n/a through <= 1.3.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2025-58670 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-58670 is a high-severity vulnerability in Shankaranand Maurya WP Content Protection, published on 22 Sep 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-58670 in the wild and no public exploit code.

Affected product: Shankaranand Maurya WP Content Protection. 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-58670/ (Markdown: https://insights.sbomify.com/CVE-2025-58670/index.md)
```

## Sources

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

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