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.
Security readout for executives and security teams
Plain-English summary
MajorDoMo can be compromised through its update mechanism if an attacker reaches the vulnerable saverestore administration path. The issue lets unauthenticated attackers redirect updates to attacker-controlled content, causing arbitrary files to be placed under the web root. This can lead to full system compromise of affected MajorDoMo deployments.
Executive priority
Treat this as urgent for any exposed MajorDoMo deployment. The vulnerability can convert unauthenticated web access into arbitrary server-side code execution, and the version scope is not clearly bounded in the supplied sources.
Technical view
The vulnerability is an unauthenticated supply-chain RCE in MajorDoMo’s saverestore/update flow. The source bundle says request input is trusted for admin mode handling, update feed validation is weak, TLS verification is disabled for downloads, and extracted update contents are copied into the document root. A fix PR exists, but affected version and release status are incomplete.
Likely exposure
Exposure is most likely on internet-reachable MajorDoMo instances where the vulnerable saverestore/update functionality is accessible. The provided affected-version data lists MajorDoMo with unclear version coverage, so teams should treat all unverified MajorDoMo deployments as potentially exposed until checked against vendor guidance.
Exploitation context
The CVE has CVSS 9.8 with network, low-complexity, unauthenticated exploitation characteristics. The source bundle does not include KEV status or cited evidence of active exploitation, so active exploitation should not be asserted from these sources alone.
Researcher notes
Key research areas are authentication bypass in saverestore mode handling, update URL trust boundaries, TLS verification behavior, archive extraction, and document-root copy behavior. Avoid assuming a specific fixed release unless confirmed by the vendor or referenced PR status.
Mitigation direction
Check upstream MajorDoMo guidance and the referenced fix PR before changing production systems.
Update to a fixed upstream release when the vendor provides one.
Restrict external access to MajorDoMo administrative and update-related paths.
Disable or tightly control automatic update behavior until patched.
Review update-source configuration for unexpected or untrusted URLs.
Validation and detection
Inventory all MajorDoMo deployments and confirm their exposed network paths.
Verify whether the referenced fix is present in deployed code.
Check update configuration for attacker-controlled or unfamiliar feed URLs.
Review webroot contents for unexpected PHP or recently added files.
Inspect access and update logs for suspicious unauthenticated update activity.
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 · low confidence lookup
CWE-494: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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.
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.
2CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
2 official scores
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-494 · source CWE mapping
Download of Code Without Integrity Check
Download of Code Without Integrity Check represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.