CVE-2026-6562
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 · uneditedA flaw has been found in dameng100 muucmf 1.9.5.20260309. Impacted is the function getListByPage of the file /index/Search/index.html. Executing a manipulation of the argument keyword can lead to sql injection. The attack may be performed from remote. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
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 · moderate confidenceSQL injection vulnerability in dameng100 muucmf 1.9.5.20260309 allows remote attackers to inject malicious SQL queries via the keyword parameter in the getListByPage function of /index/Search/index.html.
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 the installed muucmf versionCheck the application version file or admin panel for the exact muucmf version number. Look for version.php, version.json, or the admin dashboard About section.Affected if The installed version matches 1.9.5.20260309 exactly or is a variant of the 1.9.5.20260309 release.
-
Locate the vulnerable Search componentVerify the file /index/Search/index.html or /index/Search/index.php exists in the web root directory of the muucmf installation.Affected if The Search module directory and index file are present in the application structure.
-
Confirm getListByPage function uses the keyword parameterExamine the source code of the Search index file and locate the getListByPage function. Verify that it directly uses a 'keyword' parameter in SQL queries without apparent parameterization.Affected if The getListByPage function processes the keyword parameter and includes it in raw SQL queries without prepared statements or escaping.
-
Test the keyword parameter for SQL injectionIf authorized, send a crafted request to /index/Search/index.html with a keyword value containing SQL syntax (e.g., keyword=1' OR '1'='1). Observe whether the application returns database errors or unexpected data.Affected if The application reflects SQL syntax in errors, returns different data based on the injection payload, or exhibits timing delays consistent with blind SQL injection.
A user is affected if they run muucmf version 1.9.5.20260309 with the Search module enabled and the getListByPage function processes the keyword parameter without SQL parameterization.
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 dataImplement parameterized queries or prepared statements for the keyword parameter in the getListByPage function. Until a vendor patch is available, consider deploying a WAF rule to filter SQL injection payloads in the Search functionality.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6562 — 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-6562 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