MajorDoMo Unauthenticated Module Uninstall via Market 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.797% 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 |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | MajorDoMo (aka Major Domestic Module) allows unauthenticated arbitrary module uninstallation through the market module. The market module's admin() method reads gr('mode') from $_REQUEST and assigns it to $this->mode at the start of execution, making all mode-gated code paths reachable without authentication via the /objects/?module=market endpoint. The uninstall mode handler calls uninstallPlugin(), which deletes module records from the database, executes the module's uninstall() method via eval(), recursively deletes the module's directory and template files using removeTree(), and removes associated cycle scripts. An attacker can iterate through module names and wipe the entire MajorDoMo installation with a series of unauthenticated GET requests. | |
| Title | MajorDoMo Unauthenticated Module Uninstall via Market Endpoint | |
| First Time appeared |
Sergejey
Sergejey majordomo |
|
| Weaknesses | CWE-862 | |
| CPEs | cpe:2.3:a:sergejey:majordomo:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Sergejey
Sergejey majordomo |
|
| References |
| |
| Metrics |
cvssV3_1
|