CVE-2025-46578
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 · uneditedThere are SQL injection vulnerabilities in multiple interfaces of the GoldenDB database product. Attackers can exploit these interfaces to inject commands and extract sensitive database information.
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 vulnerabilities exist in multiple interfaces of the GoldenDB distributed database product. Attackers can exploit these vulnerabilities by injecting malicious SQL commands through user input in the affected interfaces, allowing unauthorized access to and extraction of sensitive database information.
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>= 6.1.03, < 6.1.03.11= 7.2.01.01CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 the installed GoldenDB versionRun the GoldenDB version command (e.g., 'goldendb --version' or check the product release documentation) or inspect the version file in the installation directoryAffected if The installed version is >= 6.1.03 and < 6.1.03.11, or equals exactly 7.2.01.01
-
Determine if the affected interfaces are exposedReview network configuration and accessible database interfaces. Check which application interfaces or API endpoints connect to the GoldenDB instanceAffected if User-facing interfaces or APIs that accept input and communicate with the database are directly accessible without proper network segmentation
-
Check for input validation on database-facing interfacesInspect the configuration or code of applications using the affected interfaces. Look for direct use of user-supplied input in SQL queries without sanitization or parameterized queriesAffected if Applications pass user input directly into SQL queries without using prepared statements, parameterized queries, or input validation routines
-
Audit database user privileges and access controlsReview the database user permissions and role configurations in GoldenDB to determine if interface users have broader access than necessaryAffected if Database users associated with the affected interfaces have elevated privileges that could allow exfiltration of sensitive data if SQL injection succeeds
-
Review recent access logs for anomalous SQL patternsExamine GoldenDB query logs or audit logs for unusual SQL syntax, especially where user input might appear unescaped in query statementsAffected if Logs contain queries with unexpected SQL syntax, UNION statements, or patterns indicative of SQL injection attempts
A system is affected if it runs GoldenDB version 6.1.03 through 6.1.03.10 (inclusive) or version 7.2.01.01, and has user-accessible interfaces that pass input directly into SQL queries without parameterization.
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.
dbcve · scoped6.1.03.11
Remediate by implementing parameterized queries or prepared statements across all database interaction points in the affected interfaces, and perform comprehensive input validation on all user-supplied data before incorporating it into SQL queries.
6.1.03.11 (for 6.x branch); contact ZTE for 7.x branch fix
- Identify the current GoldenDB version in use by checking the system or consulting inventory documentation
- For version 6.1.x (where x >= 0 and x < 11): Upgrade to version 6.1.03.11 or later to resolve the SQL injection vulnerabilities
- For version 7.2.01.01: Contact ZTE technical support (support.zte.com.cn) to obtain the appropriate patched version or patch
- After upgrading, verify the SQL injection vulnerabilities are remediated by reviewing release notes or consulting with ZTE support
- Test the upgraded system in a non-production environment before deploying to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.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 $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46578 — 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-46578 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