# CVE-2025-6213: Nginx Cache Purge Preload <= 2.1.1 - Authenticated (Administrator+) Remote Code Execution

> Authenticated administrators can execute arbitrary code on the server via insufficient sanitization in the Nginx Cache Purge Preload plugin.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jul 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-7653-r8cq-rf8w

## What is CVE-2025-6213?

CVE-2025-6213 is a high-severity code injection vulnerability in psauxit Nginx Cache Purge Preload, published on 22 Jul 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Nginx Cache Purge Preload plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 2.1.1 via the 'nppp_preload_cache_on_update' function. This is due to insufficient sanitization of the $_SERVER['HTTP_REFERERER'] parameter passed from the 'nppp_handle_fastcgi_cache_actions_admin_bar' function. This makes it possible for authenticated attackers, with Administrator-level access and above, to execute code on the server.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2025-6213 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6213 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-6213 is a high-severity code injection vulnerability in psauxit Nginx Cache Purge Preload, published on 22 Jul 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6213 exists.

Affected product: psauxit Nginx Cache Purge Preload. 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-6213/ (Markdown: https://insights.sbomify.com/CVE-2025-6213/index.md)
```

## Sources

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

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