CVE-2026-27177: MajorDoMo Stored Cross-Site Scripting via Property Set Endpoint
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.
Security readout for executives and security teams
Plain-English summary
MajorDoMo has a stored XSS flaw in an unauthenticated IoT property update path. A remote attacker can save malicious content that runs automatically when an administrator opens the property editor. Because the session cookie is reported as missing HttpOnly, successful script execution could expose an admin session.
Executive priority
Treat this as a high-priority remediation for exposed MajorDoMo systems. The practical business risk is administrator session compromise and unauthorized control-plane activity in a smart-home or automation environment.
Technical view
The source bundle describes raw property values stored through /objects/?op=set and later rendered unescaped in admin UI SOURCE and VALUE fields. The issue is CWE-79 with CVSS 7.2. The affected version evidence is imprecise, and the bundle does not identify a confirmed fixed release.
Likely exposure
Exposure is most likely in MajorDoMo installations where unauthenticated property update and data endpoints are reachable from untrusted networks. Internet-facing smart-home deployments carry higher risk. Exact affected versions are not clear from the provided evidence.
Exploitation context
The bundle reports no KEV listing and provides no cited evidence of active exploitation. The attack does not require authentication and triggers when an administrator views poisoned properties, but this assessment should not be treated as confirmation of exploitation in the wild.
Researcher notes
Key gaps are affected version precision, release status of the fix, and exploitation telemetry. Validation should focus on exposure of unauthenticated endpoints, output escaping in admin rendering paths, and cookie security flags without using live exploit payloads.
Mitigation direction
Check MajorDoMo vendor guidance and the referenced fix PR for an official patched release.
Restrict unauthenticated MajorDoMo endpoints to trusted IoT networks only.
Limit admin panel access to trusted management networks.
Ensure stored property values are escaped before rendering in admin views.
Set session cookies with HttpOnly where supported by the application.
Validation and detection
Inventory MajorDoMo deployments and confirm whether exposed endpoints are reachable from untrusted networks.
Review application version and compare against vendor advisories or merged fixes.
Inspect admin property views for untrusted stored values before administrator browsing.
Confirm session cookies include HttpOnly and appropriate secure attributes.
Check logs for unexpected unauthenticated property updates or data enumeration.
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 · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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 database injection or access, so collection and exfiltration review may help. 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.
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-79 · source CWE mapping
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.