# CVE-2025-6247: Cross-site request forgery in WordPress Automatic Plugin

> Unauthenticated attackers can trick administrators into triggering CSRF to inject malicious scripts, leading to stored XSS and potential site compromise.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **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:** 26 Aug 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-wj4r-j458-wpf8

## What is CVE-2025-6247?

CVE-2025-6247 is a medium-severity vulnerability in ValvePress WordPress Automatic Plugin, published on 26 Aug 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

The WordPress Automatic Plugin plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.118.0. This is due to missing or incorrect nonce validation on one of its functions. This makes it possible for unauthenticated attackers to update campaigns and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Weakness: CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page)

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


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

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

## Is CVE-2025-6247 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-6247 is a medium-severity vulnerability in ValvePress WordPress Automatic Plugin, published on 26 Aug 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-6247 in the wild and no public exploit code.

Affected product: ValvePress WordPress Automatic Plugin. 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-6247/ (Markdown: https://insights.sbomify.com/CVE-2025-6247/index.md)
```

## Sources

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

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