dbcve.org
MajordomoApplication · Mjdm

CVE-2026-27179

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-18
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
MajorDoMo (aka Major Domestic Module) contains an unauthenticated SQL injection vulnerability in the commands module. The commands_search.inc.php file directly interpolates the $_GET['parent'] parameter into multiple SQL queries without sanitization or parameterized queries. The commands module is loadable without authentication via the /objects/?module=commands endpoint, which includes arbitrary modules by name and calls their usual() method. Time-based blind SQL injection is exploitable using UNION SELECT SLEEP() syntax. Because MajorDoMo stores admin passwords as unsalted MD5 hashes in the users table, successful exploitation enables extraction of credentials and subsequent admin panel access.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

MajorDoMo contains an unauthenticated time-based blind SQL injection vulnerability in commands_search.inc.php. The $_GET['parent'] parameter is directly interpolated into SQL queries without sanitization or parameterized queries. The commands module is accessible without authentication via /objects/?module=commands, allowing remote attackers to exploit the SQL injection using UNION SELECT SLEEP() syntax and extract unsalted MD5 password hashes from the users table.

MitigationReplace direct parameter interpolation with prepared statements/parameterized queries in commands_search.inc.php. Additionally, implement proper input validation and migrate password storage to salted bcrypt or Argon2 hashing.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MajordomoApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm MajorDoMo installation
    Locate the web application root directory and verify commands_search.inc.php exists in the modules or include path (typically in a /modules/commands/ or /inc/ directory)
    Affected if The file commands_search.inc.php is present in the installation
  2. Verify commands module is accessible
    Attempt to access /objects/?module=commands or similar URL path that serves the commands module without requiring login credentials
    Affected if The commands module endpoint is reachable without authentication
  3. Check for unsanitized parent parameter usage
    Examine commands_search.inc.php source code and look for direct use of $_GET['parent'] in SQL queries without prepared statements, sanitization functions, or parameterized queries
    Affected if $_GET['parent'] is directly interpolated into SQL queries without escaping or parameter binding
  4. Inspect password storage mechanism
    Examine the users table schema or user model code to verify if passwords are stored as unsalted MD5 hashes
    Affected if Passwords are stored as unsalted MD5 hashes in the users table
  5. Test for SQL injection vulnerability
    Send a crafted request to the commands module with parent parameter containing SQL injection payload such as '1 UNION SELECT SLEEP(5)-- and measure response time
    Affected if The application exhibits delayed responses indicating successful time-based blind SQL injection

A user is affected if MajorDoMo is installed with commands_search.inc.php present, the commands module is accessible without authentication, and $_GET['parent'] is used directly in SQL queries without sanitization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Replace direct parameter interpolation with prepared statements/parameterized queries in commands_search.inc.php. Additionally, implement proper input validation and migrate password storage to salted bcrypt or Argon2 hashing.

Recommended fix Moderate confidence
  1. 1. Navigate to the GitHub repository: https://github.com/sergejey/majordomo
  2. 2. Locate and review PR #1177 which contains the vendor patch for this SQL injection vulnerability
  3. 3. Examine the changes made to commands_search.inc.php in the patch - look for proper sanitization/parameterization of the $_GET['parent'] parameter
  4. 4. Apply the patch changes to your local installation, ensuring the parent parameter is now sanitized or converted to a parameterized query before being used in SQL statements
  5. 5. Alternatively, download the latest code from the repository after the patch was merged
  6. 6. Verify the fix by testing the /objects/?module=commands endpoint with the parent parameter to ensure SQL injection is no longer possible
  7. 7. After patching, consider migrating away from MD5 password hashing to a more secure method (e.g., bcrypt, Argon2)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Majordomo Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27179 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-27179 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data