MajorDoMo Stored Cross-Site Scripting via Property Set Endpoint
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| sergejey | MajorDoMo | unknown |
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Sergejey | Majordomo |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.229% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Mjdm
Mjdm majordomo |
|
| CPEs | cpe:2.3:a:mjdm:majordomo:-:*:*:*:*:*:*:* | |
| Vendors & Products |
Mjdm
Mjdm majordomo |
|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | MajorDoMo Stored Cross-Site Scripting via Property Set Endpoint | |
| First Time appeared |
Sergejey
Sergejey majordomo |
|
| Weaknesses | CWE-79 | |
| CPEs | cpe:2.3:a:sergejey:majordomo:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Sergejey
Sergejey majordomo |
|
| References |
| |
| Metrics |
cvssV3_1
|