CVE-2026-10606
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 vulnerability was determined in DedeCMS 5.7.88. The affected element is the function TrimMsg of the file /plus/feedback.php of the component Feedback Handler. Executing a manipulation of the argument msg can lead to sql injection. The attack can be launched remotely. The exploit has been publicly disclosed and may be utilized.
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 confidenceSQL injection vulnerability in DedeCMS 5.7.88 in the TrimMsg function within /plus/feedback.php. The msg parameter passed to the Feedback Handler component is not properly sanitized, allowing remote attackers to inject arbitrary SQL queries.
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.
-
Confirm DedeCMS installation and versionCheck the version.php or common.inc.php file in the DedeCMS root directory for the version string, or look for a version marker in the admin dashboard about pageAffected if The installed version matches 5.7.88 or falls within an unpatched version range of DedeCMS 5.7.x
-
Verify feedback.php exists and is accessibleInspect the /plus/feedback.php file on the web server to confirm its presence, and test if the endpoint responds to HTTP requestsAffected if The file /plus/feedback.php exists and is accessible via the web server
-
Check if feedback module is enabledExamine the DedeCMS admin panel under module management or check the database for feedback-related configuration settings in the dede_sysconfig tableAffected if The feedback module is installed and enabled in the CMS configuration
-
Inspect TrimMsg function for input validationOpen /plus/feedback.php and locate the TrimMsg function definition; examine whether the $msg parameter undergoes proper escaping, parameterized queries, or whitelist validation before database useAffected if The TrimMsg function does not use parameterized queries or proper escaping on the msg parameter
-
Review web server logs for SQL injection attemptsSearch access logs for requests to /plus/feedback.php containing common SQL injection patterns in the msg parameter such as UNION, SELECT, OR 1=1, or stacked queriesAffected if Logs show suspicious requests with SQL injection payloads targeting the msg parameter in feedback.php
A user is affected if they are running DedeCMS version 5.7.88 with the feedback module enabled and the /plus/feedback.php file accessible, where the TrimMsg function lacks proper input sanitization on the msg parameter.
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) in the TrimMsg function and implement proper input validation for the msg parameter before database operations.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10606 — 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-10606 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