# CVE-2026-27174: MajorDoMo Unauthenticated Remote Code Execution via Admin Console Eval

> Unauthenticated attackers can execute arbitrary PHP code via the admin console due to missing authentication checks and unsafe eval usage.

- **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-8p47-wg5j-hm56

## What is CVE-2026-27174?

CVE-2026-27174 is a critical code injection 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) allows unauthenticated remote code execution via the admin panel's PHP console feature. An include order bug in modules/panel.class.php causes execution to continue past a redirect() call that lacks an exit statement, allowing unauthenticated requests to reach the ajax handler in inc_panel_ajax.php. The console handler within that file passes user-supplied input from GET parameters (via register_globals) directly to eval() without any authentication check. An attacker can execute arbitrary PHP code by sending a crafted GET request to /admin.php with ajax_panel, op, and command parameters.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Mjdm Majordomo.

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

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

## Is CVE-2026-27174 being exploited?

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

Public exploit code:

- MajorDoMo Console Eval Unauthenticated RCE (metasploit)
- CVE-2026-27174 - An unauthenticated remote code execution via the admin panel's PHP console feature (github_poc): https://github.com/MaxMnMl/majordomo-CVE-2026-27174-poc
- MajorDoMo - Unauthenticated RCE (nuclei): http/cves/2026/CVE-2026-27174.yaml

## 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-27180](https://insights.sbomify.com/CVE-2026-27180/): MajorDoMo Supply Chain Remote Code Execution via Update URL Poisoning (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-27174 and fix it if it is affected.

What it is: CVE-2026-27174 is a critical code injection 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-27174 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-27174/ (Markdown: https://insights.sbomify.com/CVE-2026-27174/index.md)
```

## Sources

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

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