CVE-2026-10607
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 identified in DedeCMS 5.7.88. The impacted element is the function dede_htmlspecialchars of the file /plus/flink.php. The manipulation of the argument msg leads to sql injection. The attack may be initiated remotely. The exploit is publicly available and might be used.
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 DedeCMS 5.7.88 in the /plus/flink.php file. The dede_htmlspecialchars function fails to properly sanitize the 'msg' parameter, allowing attackers to inject malicious SQL queries remotely.
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 DedeCMS installation and versionCheck for DedeCMS by looking for characteristic files (e.g., /include/common.inc.php, /dede/login.php) and examine version files or admin panels for version number 5.7.88Affected if DedeCMS version is 5.7.88 or falls within the affected range without patch applied
-
Verify /plus/flink.php existsCheck if the file /plus/flink.php exists in the web root directoryAffected if The file exists and is web-accessible
-
Confirm flink feature is accessibleAttempt to access the flink.php page directly via HTTP request or check if the friend link module is enabled in the CMS configurationAffected if The flink.php page is accessible without authentication or the flink module is active
-
Check msg parameter handlingReview the source code of /plus/flink.php, specifically looking at how the msg parameter is processed through the dede_htmlspecialchars function - verify if it is used in SQL queries without proper sanitization or parameterizationAffected if The msg parameter is used in SQL queries without prepared statements/parameterized queries or adequate escaping
-
Test for SQL injection vulnerabilityIf permitted by authorized security testing, send a crafted request to /plus/flink.php with sql injection payloads in the msg parameter (e.g., msg=1' OR '1'='1) and observe database responses or errorsAffected if The application returns database errors or exhibits unexpected behavior indicating SQL injection is possible
A user is affected if they run DedeCMS version 5.7.88 (or an unpatched version) with the flink module accessible and the msg parameter in /plus/flink.php used in unsanitized 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 dataApply input validation and parameterized queries to the msg parameter in flink.php, or update to a patched version of DedeCMS if available. Review and fix the dede_htmlspecialchars function to ensure proper SQL sanitization.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10607 — 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-10607 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