{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-27181 exists.","fix":"No fix has been published for CVE-2026-27181 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-27181 is a high-severity missing authorization vulnerability in sergejey MajorDoMo, published on 18 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-27181 and fix it if it is affected.\n\nWhat it is: CVE-2026-27181 is a high-severity missing authorization vulnerability in sergejey MajorDoMo, published on 18 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-27181 exists.\n\nAffected product: sergejey MajorDoMo. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-27181/ (Markdown: https://insights.sbomify.com/CVE-2026-27181/index.md)","id":"CVE-2026-27181","markdown":"https://insights.sbomify.com/CVE-2026-27181/index.md","name":"CVE-2026-27181","record":{"aliases":["GHSA-5v24-5hr7-xg26"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_modify","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Home automation platform","requires_auth":"none","summary":"Unauthenticated attackers can uninstall arbitrary modules and wipe the MajorDoMo installation via the market endpoint.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"majordomo","vendor":"mjdm"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"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-\u003emode 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"MajorDoMo Unauthenticated Module Uninstall via Market Endpoint","id":"CVE-2026-27181","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Saturn Remote Mouse Server UDP Command Injection RCE","id":"CVE-2026-27182"},"packages":[],"prev":{"headline":"MajorDoMo Supply Chain Remote Code Execution via Update URL Poisoning","id":"CVE-2026-27180"},"products":["MajorDoMo"],"published":"2026-02-18","related":[{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2023-50917","kev_date_added":null,"published":"2023-12-15"},{"cvss_score":9.3,"headline":"MajorDoMo Unauthenticated Remote Code Execution via Admin Console Eval","id":"CVE-2026-27174","kev_date_added":null,"published":"2026-02-18"},{"cvss_score":9.3,"headline":"MajorDoMo Supply Chain Remote Code Execution via Update URL Poisoning","id":"CVE-2026-27180","kev_date_added":null,"published":"2026-02-18"},{"cvss_score":9.2,"headline":"MajorDoMo Command Injection in rc/index.php via Race Condition","id":"CVE-2026-27175","kev_date_added":null,"published":"2026-02-18"},{"cvss_score":8.8,"headline":"MajorDoMo Unauthenticated SQL Injection in Commands Module","id":"CVE-2026-27179","kev_date_added":null,"published":"2026-02-18"},{"cvss_score":5.3,"headline":"MajorDoMo Stored Cross-Site Scripting via Property Set Endpoint","id":"CVE-2026-27177","kev_date_added":null,"published":"2026-02-18"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-23","vendors":["sergejey"]},"summary":"Unauthenticated attackers can uninstall arbitrary modules and wipe the MajorDoMo installation via the market endpoint.","url":"https://insights.sbomify.com/CVE-2026-27181/"}