Cadmium CMS
CVE-2025-51511
CRITICAL
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain backend/admin session
-
DeliveryAccess admin filemanager upload
-
ExploitUpload unvalidated server-side script
-
ExecutionRequest uploaded file to execute
-
ImpactCode execution and full server compromise
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 targets the administrative content filemanager upload at /admin/content/filemanager/uploads in Cadmium CMS 0.4.9; the attacker must be able to reach this backend endpoint and the server must accept and serve an executable server-side file that bypasses upload validation (CWE-434). The description's 'background' (back-office) characterization and the '/admin/' path indicate a backend/administrative feature, so a valid authenticated backend session is the most likely prerequisite - this materially limits exploitation and conflicts with the PR:N in the supplied vector, which would otherwise imply no authentication. The precise access level (unauthenticated vs. any authenticated role vs. admin only) and whether the uploaded file is placed in a web-executable path are not stated in the available sources; confirm with the vendor/source. |
| Impact | The input CVSS is 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), which models remote, unauthenticated, trivial exploitation with full confidentiality, integrity and availability impact - consistent with CWE-434 arbitrary file upload leading to code execution. However, these signals conflict with the description and should be treated cautiously: the description calls this a 'background' file upload in /admin/content/filemanager/uploads, and the '/admin/' path plus 'background' (back-office) wording strongly implies the feature is behind the CMS administrative backend, i.e. an authenticated operation. That contradicts the PR:N in the supplied vector - the network-unauthenticated scoring may be overstated; verify whether the upload endpoint is reachable without a valid backend session. The other signals temper the raw score: EPSS is 0.38% (32nd percentile), indicating low modeled probability of exploitation in the near term; there is no CISA KEV listing in the input, so there is no evidence of active exploitation; and the only exploit artifact is an unverified reference. The vuln.today decision label is act_now, so prioritization guidance in the input is high. Netting this out: the technical impact is genuinely severe (webshell/RCE class), but the real-world urgency is tempered by an obscure product, a likely authentication prerequisite not reflected in PR:N, low EPSS, and no confirmed active exploitation. |
| Exploit ScenarioDerived | An attacker with access to the Cadmium CMS administrative backend uses the content filemanager upload feature (/admin/content/filemanager/uploads) to upload a malicious server-side script (e.g. a PHP webshell) that is not properly validated, then requests the uploaded file to execute code on the server. A public PoC reference exists (a GitHub issue) but is not verified as working exploit code, so reliable weaponization is not confirmed. If the endpoint is in fact reachable without authentication - as the PR:N in the supplied vector suggests but the 'background'/admin wording contradicts - the same upload could be performed by a remote unauthenticated attacker. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 28, 2026
Arbitrary file upload in Cadmium CMS 0.4.9 through /admin/content/filemanager/uploads allows an attacker who can reach the back-office content file manager to place a server-side executable file, potentially achieving code execution with high confidentiality, integrity and availability impact. The supplied CVSS score is 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), but the independent assessment uses PR:L because the /admin/ path indicates an authenticated backend session is likely required; the exact role and whether uploads are web-executable are not stated in the available sources. A public PoC reference exists in the vendor GitHub issue but is not verified as working exploit code; active exploitation is not confirmed in CISA KEV data, EPSS is 0.38% (32nd percentile), and the vuln.today priority is act_now.
RemediationAI
No vendor-released patch was identified at time of analysis for Cadmium CMS 0.4.9, so remediation must start with compensating controls until an update is available. Restrict access to /admin/content/filemanager/uploads and the broader /admin/ back office to trusted networks or specific administrative accounts, accepting that this limits legitimate remote content administration. If file uploads are not business-critical, disable the file manager upload feature or remove write access to its upload directory, which may break content publishing workflows. Enforce server-side upload validation using an allowlist of non-executable extensions and MIME types and store uploads outside the web root, with the trade-off that existing content paths and delivery may need reconfiguration. Configure the web server to deny execution of scripts in the upload directory (for example, disable PHP/CGI handlers or block direct access), which can prevent serving legitimate uploaded media if not scoped carefully. Monitor the endpoint and upload directory for unexpected server-side files; consult https://github.com/cadmium-org/cadmium-cms/issues/23 and https://vuldb.com/vuln/337876 for vendor/source updates.
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in composer
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
CWE-434 (Unrestricted Upload of File with Dangerous Type) is the root-cause class: the application accepts a file through the administrative content filemanager endpoint /admin/content/filemanager/uploads without adequate validation of extension, MIME type or executable content. The affected CPE is cpe:2.3:a:cadmium-cms:cadmium_cms:0.4.9:*:*:*:*:*:*:*, identifying Cadmium CMS 0.4.9 only. The sources do not describe the exact validation bypass, the required role, or whether uploaded files are stored in a web-executable path; the trigger and post-upload execution path are not stated. The /admin/ path and 'background' (back-office) wording point to an administrative feature, which is why the independent assessment treats a valid backend session as the most likely prerequisite and lowers the assessed privilege requirement from PR:N to PR:L. A public GitHub issue is referenced as the PoC/advisory source (https://github.com/cadmium-org/cadmium-cms/issues/23) and VulDB lists an advisory (https://vuldb.com/vuln/337876), but neither supplied reference confirms a working exploit chain.
Know when Cadmium 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:N/UI:N/S:U/C:H/I:H/A:H
Network-reachable admin filemanager upload requiring a backend session (PR:L, not PR:N); arbitrary file upload yields code execution with full C/I/A impact, scope unchanged.
Primary rating from Vendor (mitre).
CVSS VectorVendor: mitre
DescriptionCVE.org
Cadmium CMS v.0.4.9 has a background arbitrary file upload vulnerability in /admin/content/filemanager/uploads.
Executive ViewAI
CVE-2025-51511 is a critical vulnerability in Cadmium CMS 0.4.9 that could allow an authenticated attacker with back-office access to upload and execute malicious files, potentially leading to full system compromise. Although no active exploitation has been confirmed and the public exploit reference is unverified, the high severity and potential for significant data breach, service disruption, and reputational damage make this a priority for security management.
No vendor-released patch identified at time of analysis. Interim mitigations include restricting access to the affected endpoint, enforcing strong authentication, disabling file uploads if feasible, and implementing web application firewall rules to block malicious file uploads.
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.
NVD
CVE.org
EPSS
GitHub
VulDB
Exploit-DB