CVE-2025-67288: An arbitrary file upload vulnerability in Umbraco CMS v16.3.3 allows attackers to execute arbitrary code by...
An arbitrary file upload vulnerability in Umbraco CMS v16.3.3 allows attackers to execute arbitrary code by uploading a crafted PDF file. NOTE: this is disputed by the Supplier because the responsibility for file validation (as shown in the documentation) belongs to the system administrator who is implementing Umbraco CMS in their environment, not to Umbraco CMS itself. The Supplier also states that PDF JavaScript runs in a completely isolated sandbox, not the browser's DOM context, which means that privilege boundaries would not be crossed, a related issue to CVE-2023-49279.
Security readout for executives and security teams
Plain-English summary
This CVE claims an Umbraco CMS 16.3.3 file upload issue could lead to code execution through a crafted PDF. The supplier disputes the finding, saying validation is implementer responsibility and PDF JavaScript is sandboxed. Treat this as a high-attention exposure question, not a confirmed platform-wide emergency.
Executive priority
Prioritize verification this week for internet-facing Umbraco sites with upload features. Escalate only if your implementation allows risky PDF upload, processing, or serving behavior.
Technical view
The record maps to CWE-434 with CVSS 10.0 and a network, unauthenticated, no-user-interaction vector. However, affected vendor/product fields are listed as n/a, the only reference is a public GitHub report, and the supplier disputes both impact and responsibility boundaries.
Likely exposure
Potentially relevant only to Umbraco CMS 16.3.3 deployments that allow PDF uploads or custom media/file handling. Exposure depends on local validation, storage, rendering, and execution controls.
Exploitation context
No CISA KEV listing is reported in the bundle. The provided sources do not establish active exploitation. A public GitHub reference exists, but the supplier disputes the vulnerability and impact model.
Researcher notes
The core uncertainty is vulnerability validity. The CVE asserts arbitrary code execution, while the supplier disputes privilege-boundary impact and responsibility. Avoid treating CVSS 10.0 as fully validated without local evidence.
Mitigation direction
Review Umbraco and vendor guidance before applying assumptions about platform fixes.
Restrict PDF uploads to trusted roles and necessary workflows.
Enforce server-side file type, size, and content validation.
Store uploaded files outside executable paths where possible.
Disable PDF JavaScript handling in viewers where feasible.
Log and review recent PDF upload activity.
Validation and detection
Inventory Umbraco CMS instances and confirm any 16.3.3 deployments.
Identify public or unauthenticated upload paths accepting PDF files.
Review custom upload validators and media handling code.
Confirm uploaded PDFs cannot execute as server-side code.
Check logs for unusual PDF uploads or processing errors.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-434: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-434 · source CWE mapping
Unrestricted Upload of File with Dangerous Type
Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.