Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate to Hytale Modding Wiki
-
DeliveryUpload file with image MIME content and .php extension
-
ExploitBypass MIME validation check via content inspection
-
ExecutionAccess uploaded .php file via public URL
-
ImpactExecute arbitrary PHP code on server
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 | Requires authenticated access to Hytale Modding Wiki v1.2.0 or earlier. Attacker must upload a file with PHP content disguised as allowed MIME type (e.g., image) but with .php extension. No victim interaction needed. Executed on public-accessible disk. |
| Impact | This vulnerability presents significant real-world risk despite requiring authentication (CVSS PR:L). The CVSS 4.0 score of 8.7 reflects critical impact across confidentiality, integrity, and availability (VC:H/VI:H/VA:H) with network-based attack vector (AV:N) and low attack complexity (AC:L). SSVC framework assessment confirms proof-of-concept exploit code exists with total technical impact, though exploitation is not automatable, requiring authenticated access and manual file crafting. The absence of CISA KEV listing indicates no confirmed active exploitation at time of analysis. However, the combination of public POC availability, straightforward exploitation mechanics, and direct RCE capability makes this a genuine priority for organizations running affected versions. The primary risk mitigation is that exploitation requires valid authenticated credentials (PR:L), reducing exposure compared to unauthenticated RCE vulnerabilities. No vendor-released patch identified at time of analysis significantly elevates operational risk, as defenders lack a complete remediation path beyond compensating controls. |
| Exploit ScenarioDerived | An authenticated attacker with low-privilege wiki contributor access logs into the Hytale Modding Wiki platform and navigates to a module utilizing the quickUpload() functionality. The attacker crafts a malicious file containing PHP webshell code but manipulates the file header bytes to produce a MIME type matching the application's allowlist (e.g., image/png or text/plain). The attacker names this file with a .php extension and uploads it through the web interface. The server's finfo-based MIME validation approves the file content while getClientOriginalExtension() preserves the .php extension in the stored filename. The file is written to the public disk storage directory, and the attacker retrieves the predictable or disclosed file URL. Accessing this URL directly through a web browser causes the web server to interpret and execute the embedded PHP code, granting the attacker remote command execution capabilities on the underlying server with web server process privileges, enabling data exfiltration, lateral movement, or full system compromise. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 02, 2026
Remote code execution in Hytale Modding Wiki version 1.2.0 and earlier allows authenticated users to upload malicious PHP files through a MIME type validation bypass. The quickUpload() endpoint performs independent validation of file content (via MIME type) and filename extension, enabling attackers to craft files with benign content signatures but executable .php extensions. Uploaded files are stored in a publicly accessible location, allowing direct URL access for server-side code execution. EPSS data unavailable; publicly available exploit code exists per SSVC assessment. No vendor-released patch identified at time of analysis.
RemediationAI
No vendor-released patch identified at time of analysis per available data sources. Organizations running Hytale Modding Wiki 1.2.0 or earlier should implement immediate compensating controls: restrict file upload functionality to highly trusted administrative users only, implement server-side file extension allowlisting that rejects executable extensions (.php, .phtml, .php5, etc.) regardless of MIME type, store uploaded files outside the web root directory with access mediated through application-controlled download handlers, and configure web server rules to prevent PHP execution in upload directories (e.g., via .htaccess or nginx location blocks). Monitor the GitHub security advisory at https://github.com/HytaleModding/wiki/security/advisories/GHSA-2xqq-6778-h4j9 for patch availability. Consider implementing content security validation that ensures both MIME type and file extension are checked against a unified allowlist before accepting uploads. Organizations unable to implement adequate controls should consider disabling file upload functionality until an official patch is released.
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
This vulnerability affects the Hytale Modding Wiki application (CPE 2.3:a:hytalemodding:wiki:*:*:*:*:*:*:*:*), a documentation hosting service for Hytale game modifications. The root cause is CWE-434 (Unrestricted Upload of File with Dangerous Type), specifically an inconsistent file validation pattern. The application uses PHP's finfo library to validate file MIME types by inspecting file headers and content, but independently constructs the stored filename using Laravel's getClientOriginalExtension() method, which trusts the client-provided filename extension. This separation allows attackers to bypass content-based validation by crafting polyglot files or files with misleading headers that pass MIME allowlist checks while retaining executable .php extensions. The files are persisted to the public disk storage, making them directly accessible via web URL without additional server configuration restrictions, enabling PHP code interpretation by the web server.
Know when Wiki 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
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Primary rating from Vendor (GitHub_M) · only source for this CVE.
CVSS VectorVendor: GitHub_M
DescriptionCVE.org
The Hytale Modding Wiki is a free service for Hytale mods to host their documentation & wikis. In version 1.2.0 and prior, the quickUpload() endpoint validates uploaded files by checking their MIME type (via PHP's finfo, which inspects file contents) but constructs the stored filename using the client-supplied file extension from getClientOriginalExtension(). These two checks are independent: an attacker can upload a file whose content passes the MIME allowlist while using a .php extension. The file is stored on the public disk and is directly accessible via URL, allowing server-side code execution. At time of publication no known patches exist.
Executive ViewAI
Hytale Modding Wiki versions 1.2.0 and earlier contain a remote code execution vulnerability affecting authenticated users who can exploit a file upload bypass to execute arbitrary PHP code on the server. Organizations running this wiki software face immediate risk of server compromise, data theft, and lateral movement into internal networks, requiring urgent containment even without a vendor patch.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Disable file upload functionality entirely until patch available; (2) Implement strict WAF rules rejecting .php extensions and suspicious MIME type/extension mismatches on the quickUpload() endpoint; (3) Move upload directory outside web root or configure web server to deny PHP execution in upload directories; (4) Restrict upload access to minimal user base and require additional authentication factor; (5) Monitor upload and execution logs for unauthorized activity.
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.
Vertical privilege escalation in Wiki.js before 2.5.313 lets an account-management moderator promote themselves to full
An Insecure Direct Object Reference (IDOR) vulnerability in the Hytale Modding Wiki prior to version 1.0.0 allows any au
EUVD-2026-18499
NVD
CVE.org
EPSS
Vulnrichment
GitHub
VulDB
Exploit-DB