CVE-2026-27180: Download of Code Without Integrity Check in sergejey MajorDoMo
MajorDoMo (aka Major Domestic Module) is vulnerable to unauthenticated remote code execution through supply chain compromise via update URL poisoning. The saverestore module exposes its admin() method through the /objects/?module=saverestore endpoint without authentication because it uses gr('mode') (which reads directly from $_REQUEST) instead of the framework's $this->mode. An attacker can poison the system update URL via the auto_update_settings mode handler, then trigger the force_update handler to initiate the update chain. The autoUpdateSystem() method fetches an Atom feed from the attacker-controlled URL with trivial validation, downloads a tarball via curl with TLS verification disabled (CURLOPT_SSL_VERIFYPEER set to FALSE), extracts it using exec('tar xzvf ...'), and copies all extracted files to the document root using copyTree(). This allows an attacker to deploy arbitrary PHP files, including webshells, to the webroot with two GET requests.
AI Analysis
Technical Summary
CVE-2026-27180 is a critical vulnerability in the MajorDoMo home automation platform maintained by sergejey. The vulnerability stems from the saverestore module exposing its admin() method via the /objects/?module=saverestore endpoint without any authentication. This occurs because the code uses gr('mode'), which reads directly from the global $_REQUEST variable, instead of the framework's safer $this->mode property, allowing attackers to manipulate the mode parameter. An attacker can exploit this by poisoning the system update URL through the auto_update_settings mode handler. Subsequently, the attacker triggers the force_update handler, initiating the update chain. The autoUpdateSystem() method fetches an Atom feed from the attacker-controlled URL with minimal validation, then downloads a tarball using curl with CURLOPT_SSL_VERIFYPEER set to FALSE, disabling TLS certificate verification. The tarball is extracted using a system call to 'tar xzvf', and the extracted files are copied to the web document root via copyTree(). This process enables an attacker to deploy arbitrary PHP files, including webshells, effectively achieving unauthenticated remote code execution on the server with only two crafted GET requests. The vulnerability has a CVSS 4.0 score of 9.3 (critical), reflecting its network attack vector, no required privileges or user interaction, and high impact on confidentiality, integrity, and availability. No known exploits are reported in the wild yet, but the ease of exploitation and severity make it a significant threat. No patches are currently linked, so mitigation relies on configuration changes and monitoring until official fixes are released.
Potential Impact
For European organizations using MajorDoMo, this vulnerability poses a severe risk of full system compromise. Attackers can remotely execute arbitrary code without authentication, leading to potential data theft, system manipulation, or use of the compromised system as a pivot point for further attacks. Given MajorDoMo's role in home and building automation, attackers could disrupt critical infrastructure controls, impacting physical security, energy management, or safety systems. The ability to deploy webshells allows persistent access and stealthy control. The lack of TLS verification in the update process also exposes organizations to man-in-the-middle attacks, increasing the risk of supply chain compromise. Organizations with internet-facing MajorDoMo instances are particularly vulnerable, and the impact extends to privacy violations and operational disruptions. The critical severity and ease of exploitation necessitate urgent attention to prevent potential widespread abuse in Europe.
Mitigation Recommendations
1. Immediately restrict access to the /objects/?module=saverestore endpoint using network-level controls such as firewalls or web application firewalls (WAFs) to prevent unauthenticated access. 2. Disable or restrict the auto-update feature until a secure patch is available. 3. Implement strict validation and sanitization of update URLs to prevent poisoning attacks. 4. Ensure TLS certificate verification is enabled during all update downloads by setting CURLOPT_SSL_VERIFYPEER to TRUE in the codebase. 5. Monitor web server logs for suspicious requests targeting the saverestore module or unusual tar extraction commands. 6. Employ application-level authentication and authorization checks on all admin-related endpoints. 7. Conduct integrity checks on update packages and consider using signed updates to prevent tampering. 8. Once available, promptly apply official patches from the vendor addressing this vulnerability. 9. Consider isolating MajorDoMo installations within segmented network zones to limit lateral movement if compromised. 10. Educate system administrators about this vulnerability and encourage proactive threat hunting for indicators of compromise.
Affected Countries
Germany, France, United Kingdom, Italy, Spain, Netherlands, Belgium, Sweden, Poland, Austria
CVE-2026-27180: Download of Code Without Integrity Check in sergejey MajorDoMo
Description
MajorDoMo (aka Major Domestic Module) is vulnerable to unauthenticated remote code execution through supply chain compromise via update URL poisoning. The saverestore module exposes its admin() method through the /objects/?module=saverestore endpoint without authentication because it uses gr('mode') (which reads directly from $_REQUEST) instead of the framework's $this->mode. An attacker can poison the system update URL via the auto_update_settings mode handler, then trigger the force_update handler to initiate the update chain. The autoUpdateSystem() method fetches an Atom feed from the attacker-controlled URL with trivial validation, downloads a tarball via curl with TLS verification disabled (CURLOPT_SSL_VERIFYPEER set to FALSE), extracts it using exec('tar xzvf ...'), and copies all extracted files to the document root using copyTree(). This allows an attacker to deploy arbitrary PHP files, including webshells, to the webroot with two GET requests.
AI-Powered Analysis
Technical Analysis
CVE-2026-27180 is a critical vulnerability in the MajorDoMo home automation platform maintained by sergejey. The vulnerability stems from the saverestore module exposing its admin() method via the /objects/?module=saverestore endpoint without any authentication. This occurs because the code uses gr('mode'), which reads directly from the global $_REQUEST variable, instead of the framework's safer $this->mode property, allowing attackers to manipulate the mode parameter. An attacker can exploit this by poisoning the system update URL through the auto_update_settings mode handler. Subsequently, the attacker triggers the force_update handler, initiating the update chain. The autoUpdateSystem() method fetches an Atom feed from the attacker-controlled URL with minimal validation, then downloads a tarball using curl with CURLOPT_SSL_VERIFYPEER set to FALSE, disabling TLS certificate verification. The tarball is extracted using a system call to 'tar xzvf', and the extracted files are copied to the web document root via copyTree(). This process enables an attacker to deploy arbitrary PHP files, including webshells, effectively achieving unauthenticated remote code execution on the server with only two crafted GET requests. The vulnerability has a CVSS 4.0 score of 9.3 (critical), reflecting its network attack vector, no required privileges or user interaction, and high impact on confidentiality, integrity, and availability. No known exploits are reported in the wild yet, but the ease of exploitation and severity make it a significant threat. No patches are currently linked, so mitigation relies on configuration changes and monitoring until official fixes are released.
Potential Impact
For European organizations using MajorDoMo, this vulnerability poses a severe risk of full system compromise. Attackers can remotely execute arbitrary code without authentication, leading to potential data theft, system manipulation, or use of the compromised system as a pivot point for further attacks. Given MajorDoMo's role in home and building automation, attackers could disrupt critical infrastructure controls, impacting physical security, energy management, or safety systems. The ability to deploy webshells allows persistent access and stealthy control. The lack of TLS verification in the update process also exposes organizations to man-in-the-middle attacks, increasing the risk of supply chain compromise. Organizations with internet-facing MajorDoMo instances are particularly vulnerable, and the impact extends to privacy violations and operational disruptions. The critical severity and ease of exploitation necessitate urgent attention to prevent potential widespread abuse in Europe.
Mitigation Recommendations
1. Immediately restrict access to the /objects/?module=saverestore endpoint using network-level controls such as firewalls or web application firewalls (WAFs) to prevent unauthenticated access. 2. Disable or restrict the auto-update feature until a secure patch is available. 3. Implement strict validation and sanitization of update URLs to prevent poisoning attacks. 4. Ensure TLS certificate verification is enabled during all update downloads by setting CURLOPT_SSL_VERIFYPEER to TRUE in the codebase. 5. Monitor web server logs for suspicious requests targeting the saverestore module or unusual tar extraction commands. 6. Employ application-level authentication and authorization checks on all admin-related endpoints. 7. Conduct integrity checks on update packages and consider using signed updates to prevent tampering. 8. Once available, promptly apply official patches from the vendor addressing this vulnerability. 9. Consider isolating MajorDoMo installations within segmented network zones to limit lateral movement if compromised. 10. Educate system administrators about this vulnerability and encourage proactive threat hunting for indicators of compromise.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-02-18T15:22:30.053Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 69962e786aea4a407ae92208
Added to database: 2/18/2026, 9:26:16 PM
Last enriched: 2/18/2026, 9:41:17 PM
Last updated: 2/19/2026, 6:04:17 PM
Views: 38
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-26339: CWE-918 Server-Side Request Forgery (SSRF) in Hyland Alfresco Transformation Service (Enterprise)
CriticalCVE-2026-26338: CWE-918 Server-Side Request Forgery (SSRF) in Hyland Alfresco Transformation Service (Enterprise)
MediumCVE-2026-26337: CWE-36 Absolute Path Traversal in Hyland Alfresco Transformation Service (Enterprise)
HighCVE-2026-2232: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in wcproducttable Product Table and List Builder for WooCommerce Lite
HighCVE-2026-1581: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in tomdever wpForo Forum
HighActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.