dbcve.org
Tduck PlatformApplication · Tduckcloud

CVE-2025-0558

CRITICAL · 9.8 CVSS v3.1 Published 2025-01-18
Fix available
A fix is available. Upgrade to after 4.0 or later.
See remediation →
100/100
Remediation priority · Urgent
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 vulnerability classified as critical was found in TDuckCloud tduck-platform up to 4.0. This vulnerability affects the function QueryProThemeRequest of the file src/main/java/com/tduck/cloud/form/request/QueryProThemeRequest.java. The manipulation of the argument color leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public 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 · high confidence

A SQL injection vulnerability exists in TDuckCloud tduck-platform (versions up to 4.0) within the QueryProThemeRequest function in QueryProThemeRequest.java. The 'color' parameter is directly incorporated into SQL queries without sanitization or parameterized query usage, allowing remote attackers to inject arbitrary SQL commands.

MitigationImplement parameterized queries or use an ORM framework properly to handle the color parameter; add input validation and whitelisting for the color field; consider deploying a WAF as a temporary compensating control until the code fix is deployed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Tduck PlatformApplication
Affected:<= 4.0

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Confirm Tduck Platform installation and version
    Locate the tduck-platform application and check the version file or build metadata. Common locations include the application root directory, WAR file, or container image. Look for version indicators such as version.properties, a pom.xml file, or the deployment archive name.
    Affected if The installed version is Tduck Platform at or below v4.0 and the application is running.
  2. Verify the QueryProThemeRequest endpoint is exposed
    Identify if the web application is accessible and check for routes related to theme functionality. The vulnerable function QueryProThemeRequest is typically exposed via a REST API endpoint that handles theme/pro-theme queries. Examine the application's API documentation or decompile the application JAR/WAR to locate the QueryProThemeRequest.java mapping.
    Affected if The web interface is publicly or internally accessible and the theme query endpoint exists in the deployed application.
  3. Identify if the 'color' parameter is accepted
    Review the application's API endpoints or decompile the QueryProThemeRequest.java file to confirm that the 'color' parameter is used in the request handling. Check the application's routing configuration for endpoints that accept a 'color' query parameter.
    Affected if The application accepts HTTP requests with a 'color' parameter to the theme query endpoint without apparent input validation.
  4. Check for database query logging or unusual database access patterns
    Review application logs and database query logs for the theme-related endpoints. Look for SQL syntax errors, time delays indicative of time-based SQL injection, or unexpected database errors that include SQL fragments in the logs.
    Affected if Logs show SQL errors or unusual query patterns when the 'color' parameter is used, indicating unsanitized input is being passed to the database.

You are affected if Tduck Platform v4.0 or below is deployed, the web interface is accessible, and the theme query functionality with the 'color' parameter is exposed to users or attackers.

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
Upgrade available Upgrade to a release after 4.0
Interim mitigation

Implement parameterized queries or use an ORM framework properly to handle the color parameter; add input validation and whitelisting for the color field; consider deploying a WAF as a temporary compensating control until the code fix is deployed.

Fix this in Tduck Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0558 — 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-2025-0558 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