# CVE-2026-27180: MajorDoMo Supply Chain Remote Code Execution via Update URL Poisoning

> Unauthenticated attackers can achieve remote code execution by poisoning the update URL to deploy arbitrary PHP files via the saverestore module.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Feb 2026
- **Updated:** 23 Jun 2026
- **Also known as:** GHSA-grp8-p6j9-9x5f

## What is CVE-2026-27180?

CVE-2026-27180 is a critical vulnerability in sergejey MajorDoMo, published on 18 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-494 (Download of Code Without Integrity Check)

## Which versions are affected by CVE-2026-27180?

It affects 1 product.


Products: Mjdm Majordomo.

## How do I fix CVE-2026-27180?

No fix has been published for CVE-2026-27180 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-27180 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-27180 exists.

Public exploit code:

- MajorDoMo Supply Chain RCE via Update Poisoning (metasploit)
- https://github.com/mbanyamer/CVE-2026-27180-MajorDoMo-unauthenticated-RCE (github_poc): https://github.com/mbanyamer/CVE-2026-27180-MajorDoMo-unauthenticated-RCE

## Other vulnerabilities in sergejey MajorDoMo

- [CVE-2023-50917](https://insights.sbomify.com/CVE-2023-50917/): Command injection in n/a (critical 9.8)
- [CVE-2026-27174](https://insights.sbomify.com/CVE-2026-27174/): MajorDoMo Unauthenticated Remote Code Execution via Admin Console Eval (critical 9.3)
- [CVE-2026-27175](https://insights.sbomify.com/CVE-2026-27175/): MajorDoMo Command Injection in rc/index.php via Race Condition (critical 9.2)
- [CVE-2026-27179](https://insights.sbomify.com/CVE-2026-27179/): MajorDoMo Unauthenticated SQL Injection in Commands Module (high 8.8)
- [CVE-2026-27181](https://insights.sbomify.com/CVE-2026-27181/): MajorDoMo Unauthenticated Module Uninstall via Market Endpoint (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-27180 and fix it if it is affected.

What it is: CVE-2026-27180 is a critical vulnerability in sergejey MajorDoMo, published on 18 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-27180 exists.

Affected product: sergejey MajorDoMo. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-27180/ (Markdown: https://insights.sbomify.com/CVE-2026-27180/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-27180
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-27180
- OSV: https://osv.dev/vulnerability/CVE-2026-27180

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-27180/
Summaries are generated and may contain mistakes; the official description above is the record.