CVE-2026-46400
Deferred Deferred - Pending Action
Remote Code Execution in HAX CMS via Malicious File Upload

Publication date: 2026-06-05

Last updated on: 2026-06-05

Assigner: GitHub, Inc.

Description
HAX CMS helps manage microsite universe with PHP or NodeJs backends. Starting in version 11.0.6 and prior to version 25.0.0, the file upload functionality in HAXCMS PHP only validates file extensions using a regex pattern without checking the actual file content or MIME type. This allows attackers to upload malicious files (e.g., PHP webshells) disguised as legitimate image files, potentially leading to remote code execution. Version 25.0.0 contains a fix for the issue.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-05
Last Modified
2026-06-05
Generated
2026-06-06
AI Q&A
2026-06-06
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
haxtheweb haxcms_php to 25.0.0 (exc)
haxtheweb haxcms_php 25.0.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-434 The product allows the upload or transfer of dangerous file types that are automatically processed within its environment.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability exists in the file upload functionality of HAXCMS PHP versions 11.0.6 up to but not including 25.0.0. The system only validates the file extension using a regex pattern and does not verify the actual file content or MIME type. This allows attackers to upload malicious files, such as PHP webshells, disguised as legitimate image files.

Because the uploaded files are saved without proper content validation, an attacker can upload a file named something like 'evil.php.jpg' containing PHP code. If the server is misconfigured, this code can be executed remotely, potentially giving the attacker control over the server.


How can this vulnerability impact me? :

The vulnerability can lead to remote code execution on the server hosting HAXCMS. An attacker who successfully uploads a malicious file can execute arbitrary code, potentially gaining full control over the server.

This can result in unauthorized access to sensitive data, disruption of services, defacement of websites, or use of the server as a launchpad for further attacks.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by checking for suspicious files uploaded to the /files/ directory that have double extensions such as .php.jpg and contain PHP code inside. Since the system only validates file extensions via regex and does not verify MIME type or file content before saving, files with disguised extensions may be present.

You can search for potentially malicious uploaded files by running commands that look for files with suspicious extensions and PHP content. For example:

  • Find files with double extensions like .php.jpg: find /path/to/haxcms/files/ -type f -name "*.php.*"
  • Check if these files contain PHP code: grep -rl "<?php" /path/to/haxcms/files/
  • Alternatively, use the 'file' command to check MIME types of uploaded files: file /path/to/haxcms/files/*

Monitoring web server logs for unusual requests to files in the /files/ directory that execute PHP code can also help detect exploitation attempts.


What immediate steps should I take to mitigate this vulnerability?

To mitigate this vulnerability immediately, you should upgrade HAXCMS PHP to version 25.0.0 or later, where the issue is fixed.

Until the upgrade is applied, implement the following steps:

  • Disable or restrict file upload functionality to trusted users only.
  • Manually validate uploaded files by checking their MIME type and file content before saving.
  • Store uploaded files outside the web root or configure the web server to serve them with Content-Disposition: attachment to prevent execution.
  • Scan the /files/ directory for any existing malicious files and remove them.
  • Review and harden web server configurations to prevent execution of files in upload directories.

How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

This vulnerability allows attackers to upload malicious files disguised as legitimate images, potentially leading to remote code execution and full server compromise.

Such a security breach can result in unauthorized access to sensitive data, which may violate data protection regulations like GDPR and HIPAA that require strict controls to protect personal and health information.

Failure to properly validate file uploads and prevent remote code execution could lead to non-compliance with these standards due to inadequate security measures and potential data breaches.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart