dbcve.org
InjectionWeakness · CWE-74

CVE-2026-10608

HIGH · 7.3 CVSS v3.1 Published 2026-06-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
A security flaw has been discovered in DedeCMS 5.7.88. This affects the function RemoveXSS of the file /plus/carbuyaction.php. The manipulation of the argument postname/des results in sql injection. The attack may be launched remotely. The exploit has been released to the public and may be used for attacks.

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 confidence

SQL injection vulnerability in DedeCMS 5.7.88's /plus/carbuyaction.php file, specifically in the RemoveXSS function. The postname/des parameters are not properly sanitized before being used in SQL queries, allowing remote attackers to inject malicious SQL commands.

MitigationReplace the RemoveXSS function with proper parameterized queries or ORM usage for database operations. Validate and sanitize all user inputs using whitelist approaches rather than attempting to filter out malicious patterns.

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 checks

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

  1. Identify DedeCMS version
    Locate the version file in your DedeCMS installation (typically includes/version.php or similar) and read the version number defined there
    Affected if version is 5.7.88 or falls within the 5.7.x range prior to patch
  2. Verify carbuyaction.php exists
    Check if the file /plus/carbuyaction.php exists in your web root directory
    Affected if the file exists and the application uses this component
  3. Locate RemoveXSS function
    Open /plus/carbuyaction.php and search for the RemoveXSS function definition or include statement
    Affected if RemoveXSS is used to sanitize the postname or des parameter before SQL queries
  4. Inspect postname/des parameter handling
    In carbuyaction.php, locate where postname or des parameters from POST/GET requests are used in SQL queries and check if RemoveXSS is the only sanitization applied
    Affected if parameters are passed directly to SQL queries after only RemoveXSS sanitization without parameterized queries
  5. Test parameter injection
    If accessible, submit a crafted request to /plus/carbuyaction.php with postname parameter containing SQL injection syntax (e.g., single quote) and observe if SQL errors are returned or behavior changes
    Affected if the application returns SQL syntax errors or responds unexpectedly to injected characters

Your environment is affected if you run DedeCMS version 5.7.88 and the /plus/carbuyaction.php file uses RemoveXSS to sanitize the postname or des parameter without parameterized queries.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace the RemoveXSS function with proper parameterized queries or ORM usage for database operations. Validate and sanitize all user inputs using whitelist approaches rather than attempting to filter out malicious patterns.

Have this fixed 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 help mitigating

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-10608 — 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-10608 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