CVE-2025-46577
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 is a SQL injection vulnerability in the GoldenDB database product. Attackers can inject commands to extract 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 confidenceA SQL injection vulnerability exists in GoldenDB database product allowing remote attackers to inject malicious SQL commands. The CVSS 7.5 score indicates the issue is exploitable over the network with low attack complexity, enabling attackers to extract 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 GoldenDB installationCheck the GoldenDB version by querying the database system. Common methods include: 1) Review installation documentation or manifest files in the GoldenDB installation directory, 2) Query the database using a client tool if accessible: SELECT VERSION(); or similar system query, 3) Check product-specific admin console or control panel for version informationAffected if The installed version falls within >= 6.1.03 and < 6.1.03.11, or equals exactly 7.2.01.01
-
Verify network exposureDetermine if the GoldenDB service is accessible from network locations. Check firewall rules, port configurations, and network ACLs to see if the database ports (typically 3306 or product-specific ports) are exposed to untrusted networks or the internetAffected if The database service is reachable from untrusted network segments or external IPs without proper filtering
-
Assess authentication mechanismsReview how users and applications authenticate to the database. Check if SQL interface accounts use password-based authentication and whether the connection allows direct SQL execution without parameterized query enforcementAffected if User authentication relies on simple credentials and the SQL interface permits raw query execution without enforced prepared statements
-
Review database account privilegesExamine the permissions granted to application database accounts. Check if accounts used by applications have excessive privileges such as SELECT on system tables, GRANT options, or access to multiple schemas beyond what the application requiresAffected if Database accounts have elevated privileges beyond what the application functionality requires, enabling an attacker to escalate access upon successful SQL injection
You are affected if your GoldenDB version is 6.1.03 through 6.1.03.10 (exclusive of 6.1.03.11) or exactly 7.2.01.01, and the SQL interface is network-accessible with accounts that can execute arbitrary SQL statements.
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
Implement parameterized queries/prepared statements, apply input validation and sanitization on all user-controlled database inputs, and restrict database account privileges to minimum required. Contact GoldenDB vendor for specific patch availability.
6.1.03.11 (for 6.x branch); contact ZTE for 7.x branch fix
- 1. Identify the current installed version of Zxcloud GoldenDB by checking the product version or consulting system documentation.
- 2. If running version 6.1.03.x (where x < 11), plan an upgrade to version 6.1.03.11 which contains the fix for this SQL injection vulnerability.
- 3. If running version 7.2.01.01, contact ZTE support (support.zte.com.cn) to obtain the specific patched version for the 7.x branch.
- 4. Before upgrading, perform a full backup of the GoldenDB database and configuration files.
- 5. Schedule a maintenance window as SQL injection vulnerabilities may require downtime for the upgrade process.
- 6. Apply the upgrade following ZTE's official upgrade documentation for GoldenDB.
- 7. After upgrade, verify the version has been successfully updated and test that the application functions normally.
- 8. Validate that the SQL injection vulnerability is remediated by reviewing release notes or consulting with ZTE support.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46577 — 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-46577 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