Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain administrator credentials
-
DeliveryAuthenticate to Pluck CMS admin panel
-
ExploitUpload shell.php8 via file management
-
ExecutionRequest uploaded file URL in browser
-
PersistWeb server executes .php8 as PHP 8
-
ImpactAchieve arbitrary remote code execution
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V5 - File Handling File type validation, storage isolation
MITRE ATT&CK
2 techniques across 2 tactics: Command and Control, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires two concurrent conditions: (1) the attacker must hold valid administrator credentials for the Pluck CMS instance - unauthenticated exploitation is not possible given the CVSS vector PR:H; and (2) the hosting server must be running PHP 8.x with the web server configured to map the .php8 extension to the PHP interpreter, which is standard on modern PHP 8 deployments. What limits exploitation: administrator authentication is the primary gate, meaning credential theft or insider access is a prerequisite; servers running only PHP 7.x without .php8 handler mappings are not vulnerable to the execution step (the file uploads but does not execute); and the attacker must have network access to the admin panel, which is sometimes restricted by IP allowlist in security-conscious deployments. There is no requirement for any non-default CMS configuration beyond the default file management feature being enabled, which it is by default in Pluck CMS. |
| Impact | The CVSS 3.1 vector CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H scores 7.2, accurately reflecting that exploitation demands administrator-level authentication - a meaningful barrier that limits opportunistic mass exploitation. Attack complexity is Low once credentials are obtained, and the upload mechanism is network-accessible. EPSS data was not provided in the intelligence input; without it, exploitation probability cannot be quantified. Critically, this is NOT in the CISA KEV catalog and no public proof-of-concept is identified in the provided data, placing it in a lower urgency tier despite the high impact metrics. The real-world risk is principally relevant to environments where admin credentials have been compromised, where insider threat is a concern, or where shared-admin deployments exist (e.g., multi-tenant CMS hosting). The server-side prerequisite of PHP 8.x is not a meaningful constraint given PHP 8.x is the current actively maintained branch and widely deployed. The overall risk profile is: high impact if an attacker reaches admin, but the PR:H requirement keeps automated or unauthenticated exploitation off the table. Organizations running Pluck CMS with multiple or externally accessible admin accounts should treat this as higher priority. |
| Exploit ScenarioDerived | An attacker who has obtained administrator credentials to a Pluck CMS 4.7.21 installation (via credential stuffing, phishing, or a compromised shared-admin account) navigates to the admin file-management interface, uploads a PHP webshell named shell.php8 containing arbitrary PHP code, and then accesses the uploaded file via its public URL. On any server where the PHP 8.x runtime maps the .php8 extension to the PHP handler, the webshell executes with web server process privileges, granting the attacker interactive remote command execution on the underlying host. No public proof-of-concept code has been identified in the provided data, but the attack path is directly derivable from the CVE description. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 05, 2026
Remote code execution in Pluck CMS through 4.7.21 is achievable by any authenticated administrator who exploits a gap in the file upload blacklist: the extension '.php8' is absent from the hardcoded deny-list in data/inc/files.php, allowing a crafted file to be stored and subsequently executed as PHP on servers running PHP 8.x. Reported by TuranSec, this CWE-434 flaw carries a CVSS 7.2 (PR:H), meaning exploitation is constrained to admin-level accounts but delivers full confidentiality, integrity, and availability impact once triggered. No public exploit code or CISA KEV listing is confirmed at time of analysis, but the bypass is trivially reproducible from the CVE description by any administrator with upload access.
RemediationAI
No vendor-released patched version has been identified in the provided references - the only reference points to the upstream GitHub repository (https://github.com/pluck-cms/pluck) without a specific advisory, commit, or tagged fix release. Administrators should monitor the Pluck CMS GitHub repository for a patch addressing this omission. As an immediate compensating control, administrators with filesystem access can manually add '.php8' to the extension blacklist in data/inc/files.php; note this is a brittle workaround that remains vulnerable to any future PHP extensions not yet enumerated (e.g., hypothetical .php9). A stronger mitigation is to reconfigure the blacklist logic to a strict whitelist of permitted extensions (e.g., jpg, png, gif, pdf, txt, zip) and reject all others - this eliminates the entire blacklist-bypass vulnerability class at the cost of restricting what file types administrators can upload. Additionally, web server configuration can be modified to prevent execution of any scripts within the CMS upload directory (using Apache's Options -ExecCGI, or nginx's fastcgi_param restrictions on the uploads path), which breaks the execution step even if a malicious file is stored.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Pluck CMS (CPE: cpe:2.3:a:pluck-cms:pluck_cms:*:*:*:*:*:*:*:*) implements file upload safety exclusively via a hardcoded extension blacklist defined in data/inc/files.php. The blacklist checks the last 4-5 characters of the uploaded filename against a fixed set: .php, php3, php4, php5, php6, php7, phtml, .phtm, .pht, .ph3, .ph4, .ph5, .asp, .cgi, .phar. This deny-list strategy is inherently brittle under CWE-434 (Unrestricted Upload of File with Dangerous Type) - any extension not explicitly enumerated passes validation unchecked. PHP 8.x introduced the '.php8' extension as a recognized PHP handler mapping, but the Pluck blacklist was never updated to include it. Because the uploaded file is stored unmodified on disk and the web server's MIME/handler configuration maps .php8 to the PHP 8 interpreter, the file executes with full web server privileges when requested. A whitelist-based approach (permitting only safe, explicitly known extensions) would eliminate this entire vulnerability class.
Know when Pluck Cms gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Admin credentials required (PR:H); upload is via web interface (AV:N); no complexity beyond authentication (AC:L); full host impact once executed.
Primary rating from Vendor (TuranSec).
CVSS VectorVendor: TuranSec
DescriptionCVE.org
Pluck CMS through 4.7.21 restricts dangerous file uploads in its admin file-management feature using a fixed blacklist in data/inc/files.php ('.php','php3','php4','php5','php6','php7','phtml','.phtm','.pht','.ph3','.ph4','.ph5','.asp','.cgi','.phar'), checked against the last 4-5 characters of the filename. The blacklist omits the '.php8' extension. An authenticated administrator can upload a file named e.g. shell.php8, which is stored unmodified and, on servers running PHP 8.x, is executed as PHP by the web server, resulting in remote code execution.
Executive ViewAI
Pluck CMS versions through 4.7.21 allow authenticated administrators to execute arbitrary code on PHP 8.x servers through a file upload bypass, with no public exploit identified at time of analysis. This vulnerability directly exposes organizations to infrastructure compromise, data theft, and service disruption through either insider threats or compromised administrator credentials.
No vendor-released patch identified at time of analysis. Restrict file upload capabilities to essential administrators only, disable uploads entirely if not needed, implement web application firewall rules to block .php8 file extensions, monitor and log all administrator upload activity, and conduct regular forensic scans of upload directories for unauthorized PHP 8 executable files.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Malicious file upload attacks exploit insufficient validation when web applications accept user-provided files.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Pluck CMS 4.7.2 allows remote attackers to execute arbitrary code via the blog form feature. Rated critical severity (CV
Pluck CMS 4.7.18 does not restrict failed login attempts, allowing attackers to execute a brute force attack. Rated crit
Zip Slip vulnerability in Pluck-CMS Pluck 4.7.15 allows an attacker to upload specially crafted zip files, resulting in
data/inc/files.php in Pluck 4.7.8 allows remote attackers to execute arbitrary code by uploading a .htaccess file that s
An issue was discovered in Pluck before 4.7.7-dev2. Rated critical severity (CVSS 9.8), this vulnerability is remotely e
An arbitrary file upload vulnerability in the component /inc/modules_install.php of Pluck-CMS v4.7.18 allows attackers t
A Cross-Site Request Forgery (CSRF) in Pluck CMS v4.7.15 allows attackers to change the password of any given user by ex
An issue was discovered in Pluck CMS 4.7.10-dev2 and 4.7.11. Rated high severity (CVSS 8.8), this vulnerability is remot
Pluck v4.7.7 allows CSRF via admin.php?action=settings. Rated high severity (CVSS 8.8), this vulnerability is remotely e
In Pluck-4.7.15 admin background a remote command execution vulnerability exists when uploading files. Rated high severi
Session Fixation vulnerability in login.php in Pluck-CMS Pluck 4.7.15 allows an attacker to sustain unauthorized access
In Pluck 4.7.16, an admin user can use the theme upload functionality at /admin.php?action=themeinstall to perform remot
EUVD-2026-53192
GHSA-fvwx-9qcr-crph
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB