CVE-2026-36962
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 · uneditedSQL Injection in MuuCMF T6 v1.9.4.20260115 allows an unauthenticated attacker to compromise the entire database, achieve unauthorized administrative access, and potentially gain remote code execution by writing malicious files to the server's file system via the keyword parameter in the /index/controller/Search.php endpoint.
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 confidenceUnauthenticated SQL injection in MuuCMF T6 v1.9.4.20260115 through the keyword parameter in /index/controller/Search.php allows attackers to inject arbitrary SQL queries, potentially exposing the entire database, hijacking administrative accounts, and achieving RCE by writing malicious files via database file write capabilities.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Identify MuuCMF T6 installationLocate the web application directory and confirm the MuuCMF T6 application is present. Check for the presence of /index/controller/Search.php file.Affected if The file /index/controller/Search.php exists in the web root.
-
Determine the installed versionCheck the application version file (commonly version.php, changelog, or composer.json in the application root) and compare it to the affected range starting from v1.9.4.20260115.Affected if The installed version is v1.9.4.20260115 or any later version prior to patching.
-
Inspect the Search.php code for SQL injection vulnerabilityOpen /index/controller/Search.php and examine how the keyword parameter is used in database queries. Look for direct string concatenation of the keyword into SQL statements without parameterized queries or input sanitization.Affected if The keyword parameter is used in SQL queries without prepared statements or input sanitization.
-
Verify the vulnerability is exploitableTest the /index/controller/Search.php endpoint with the keyword parameter using a safe SQL test payload (e.g., keyword=test' OR '1'='1) to confirm unsanitized input is accepted.Affected if The application accepts and processes unsanitized keyword parameter input in SQL queries.
A user is affected if MuuCMF T6 v1.9.4.20260115 or later is installed and the Search.php file contains unsanitized keyword parameter usage in SQL queries.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataReplace dynamic SQL queries with parameterized queries/prepared statements to sanitize the keyword parameter; also restrict database file write permissions and apply vendor patch if available.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-36962 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-36962 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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