Skip to main content
EPSS 0.2%top 93%

CVE-2026-70376: CWE-352 Cross-Site Request Forgery (CSRF) in pluck-cms Pluck CMS

0
Critical
VulnerabilityCVE-2026-70376cvecve-2026-70376cwe-352
Published: 08/05/2026 (08/05/2026, 06:58:44 UTC)
Source: CVE Database V5
Vendor/Project: pluck-cms
Product: Pluck CMS

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.

CVSS v3.1

Score 9.6critical

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Affected software

pluck-cms

Pluck CMS

Affected versions
>=0 <=4.7.21

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 08/12/2026, 14:24:26 UTC

Technical Analysis

CVE-2026-70376 identifies a Cross-Site Request Forgery (CSRF) vulnerability in Pluck CMS where the admin panel relies solely on Referer-header validation for CSRF protection. The absence of per-request anti-CSRF tokens in the admin area means that an attacker can craft malicious requests that the system may accept as legitimate, leading to unauthorized actions within the admin interface. This vulnerability is classified under CWE-352 and has a CVSS v3.1 score of 9.6 (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H), reflecting its critical severity and potential for complete compromise of the affected system.

Potential Impact

Successful exploitation can lead to unauthorized administrative actions, resulting in full compromise of confidentiality, integrity, and availability of the Pluck CMS installation. Attackers could manipulate content, change configurations, or disrupt service without needing prior authentication privileges beyond a user with UI interaction.

Mitigation Recommendations

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. 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.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
TuranSec
Date Reserved
2026-08-04T07:13:07.993Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6a72e5cbbf8831d539735231

Added to database: 08/05/2026, 07:27:07 UTC

Last enriched: 08/12/2026, 14:24:26 UTC

Last updated: 09/17/2026, 22:01:37 UTC

Views: 68

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses