CVE-2025-29085
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 · uneditedSQL injection vulnerability in vipshop Saturn v.3.5.1 and before allows a remote attacker to execute arbitrary code via /console/dashboard/executorCount?zkClusterKey component.
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 vipshop Saturn v3.5.1 and prior versions in the /console/dashboard/executorCount endpoint via the zkClusterKey parameter allows remote attackers to execute arbitrary code.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify vipshop Saturn installationLocate the Saturn application by checking for running processes, web server document roots, or service directories named 'saturn' or containing Saturn-related JAR/WAR files. Look for the console interface typically accessible on port 8080 or configured web server ports.Affected if vipshop Saturn software is found running in the environment
-
Check Saturn versionLocate the version file or JAR manifest in the Saturn installation directory. Common locations include VERSION files, build metadata in WAR/JAR files, or the startup banner output. Compare the installed version to v3.5.1 - versions 3.5.1 and earlier are affected.Affected if Installed version is v3.5.1 or any earlier version of vipshop Saturn
-
Verify vulnerable endpoint existsCheck if the /console/dashboard/executorCount endpoint is accessible by attempting a request to the application. This endpoint processes the zkClusterKey parameter and should exist in affected versions.Affected if The /console/dashboard/executorCount endpoint responds and accepts the zkClusterKey parameter without authentication
-
Review application logs for exploitation signsSearch application and database logs for suspicious SQL patterns in requests to /console/dashboard/executorCount, especially UNION-based injections, OR 1=1 patterns, or unexpected zkClusterKey values containing SQL keywords.Affected if Log analysis reveals SQL injection attempts or successful exploitation against the zkClusterKey parameter
The environment is affected if vipshop Saturn version 3.5.1 or earlier is installed and the /console/dashboard/executorCount endpoint is accessible without authentication.
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 dataUpgrade to a patched version of vipshop Saturn beyond v3.5.1; if immediate upgrade is not feasible, implement input validation and parameterized queries as compensating controls.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-29085 — 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-2025-29085 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