# CVE-2026-70376: Pluck CMS - CSRF via Spoofable Missing-Referer Bypass Leads to Stored XSS and RCE

> Attackers can bypass CSRF protections in Pluck CMS admin panel to inject stored XSS and achieve remote code execution.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **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:** 5 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-qg2j-83g4-98r4

## What is CVE-2026-70376?

CVE-2026-70376 is a critical vulnerability in pluck-cms Pluck CMS, published on 5 Aug 2026. 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

Pluck CMS's admin panel relies solely on a Referer-header comparison (requestedByTheSameDomain in data/inc/functions.admin.php, gating every admin.php action) for CSRF protection, with no per-request anti-CSRF token anywhere in the admin area.

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

## Which versions are affected by CVE-2026-70376?


## How do I fix CVE-2026-70376?

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

## Is CVE-2026-70376 being exploited?

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

Public exploit code:

- CVE-2026-70376 — Pluck CMS site-wide CSRF (fail-open Referer check) → RCE via double-extension upload. CWE-352/434, CVSS 8.0. Advisory + PoC by @IlhomjonR. (github_poc): https://github.com/IlhomjonR/CVE-2026-70376

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-70376 and fix it if it is affected.

What it is: CVE-2026-70376 is a critical vulnerability in pluck-cms Pluck CMS, published on 5 Aug 2026. 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-2026-70376 in the wild and no public exploit code.

Affected product: pluck-cms Pluck CMS. 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-2026-70376/ (Markdown: https://insights.sbomify.com/CVE-2026-70376/index.md)
```

## Sources

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

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