Skip to main content
VulnerabilityPublished Updated

CVE-2026-70376: Pluck CMS · Cross-Site Request Forgery (CSRF)

Affects Pluck CMSSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.6 Critical.

Data as of 3 Nov 2026, 22:58 UTC

CVSS 3.1 base score
9.6Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
pluck-cmsPluck CMSAffected
  • <=4.7.21
Fixed in–

AI-suggested

Until an official fix is available, administrators should consider implementing additional CSRF protections such as per-request anti-CSRF tokens or other compensating controls to mitigate the risk. Monitoring for suspicious admin actions and restricting access to the admin panel by IP or VPN may reduce exposure.

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.

References

Community reviews

Loading reviews…