# CVE-2026-27177: MajorDoMo Stored Cross-Site Scripting via Property Set Endpoint

> Attackers can inject malicious scripts via unauthenticated property updates, leading to admin session hijacking and potential code execution in MajorDoMo.

- **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-c59q-pmw5-v3pf

## What is CVE-2026-27177?

CVE-2026-27177 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 via the /objects/?op=set endpoint, which is intentionally unauthenticated for IoT device integration. User-supplied property values are stored raw in the database without sanitization. When an administrator views the property editor in the admin panel, the stored values are rendered without escaping in both a paragraph tag (SOURCE field) and a textarea element (VALUE field). The XSS fires on page load without requiring any click from the admin. Additionally, the session cookie lacks the HttpOnly flag, enabling session hijack via document.cookie exfiltration. An attacker can enumerate properties via the unauthenticated /api.php/data/ endpoint and poison any property with malicious JavaScript.

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

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

It affects 1 product.


Products: Mjdm Majordomo.

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

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

## Is CVE-2026-27177 being exploited?

There is no known exploitation of CVE-2026-27177 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-27177 and fix it if it is affected.

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

## Sources

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

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