# CVE-2026-27178: MajorDoMo Stored Cross-Site Scripting via Method Parameters to Shoutbox

> Unauthenticated attackers can inject scripts via shoutbox parameters, leading to session hijacking when administrators view the dashboard.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Feb 2026
- **Updated:** 23 Jun 2026
- **Also known as:** GHSA-5c8c-h849-76wx

## What is CVE-2026-27178?

CVE-2026-27178 is a medium-severity cross-site scripting vulnerability in sergejey MajorDoMo, published on 18 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

MajorDoMo (aka Major Domestic Module) contains a stored cross-site scripting (XSS) vulnerability through method parameter injection into the shoutbox. The /objects/?method= endpoint allows unauthenticated execution of stored methods with attacker-controlled parameters. Default methods such as ThisComputer.VolumeLevelChanged pass the user-supplied VALUE parameter directly into the say() function, which stores the message raw in the shouts database table without escaping. The shoutbox widget renders stored messages without sanitization in both PHP rendering code and HTML templates. Because the dashboard widget auto-refreshes every 3 seconds, the injected script executes automatically when any administrator loads the dashboard, enabling session hijack through cookie exfiltration.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Mjdm Majordomo.

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

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

## Is CVE-2026-27178 being exploited?

There is no known exploitation of CVE-2026-27178 in the wild and no public exploit code.

## 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-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)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-27178 is a medium-severity cross-site scripting vulnerability in sergejey MajorDoMo, published on 18 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-27178 in the wild and no public exploit code.

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-27178/ (Markdown: https://insights.sbomify.com/CVE-2026-27178/index.md)
```

## Sources

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

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