dbcve.org
Zxcloud GoldendbApplication · Zte

CVE-2025-46579

HIGH · 7.8 CVSS v3.1 Published 2025-04-27
Fix available
A fix is available. Upgrade to 6.1.03.11 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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
There is a DDE injection vulnerability in the GoldenDB database product. Attackers can inject DDE expressions through the interface, and when users download and open the affected file, the DDE commands can be executed.

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

DDE (Dynamic Data Exchange) injection vulnerability in GoldenDB database product allows attackers to inject malicious DDE expressions through the interface. When users download and open the affected file, the embedded DDE commands can be automatically executed, potentially leading to command execution on the victim's machine.

MitigationImplement strict input validation and sanitization to prevent DDE expressions from being embedded in exported files; consider warning dialogs or disabling DDE auto-update features in generated files; educate users about risks of opening files from untrusted sources.

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
Zxcloud GoldendbApplication
Affected:>= 6.1.03, < 6.1.03.11= 7.2.01.01

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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. Identify GoldenDB installation
    Locate GoldenDB installation directories or running processes. Common paths may include /opt/goldendb, /usr/local/goldendb, or check for goldendb service processes using commands like 'ps aux | grep -i goldendb' or 'systemctl list-units | grep -i goldendb'. Check for installation under the Zte Zxcloud product directories.
    Affected if GoldenDB is installed and running
  2. Determine installed GoldenDB version
    Run version detection command specific to GoldenDB. Common methods include: checking 'goldendb --version', viewing version files in installation directory, querying the database with 'SELECT VERSION()' or 'SELECT @@version', or checking manifest/version configuration files in the installation path.
    Affected if Version falls within >= 6.1.03, < 6.1.03.11 or equals 7.2.01.01
  3. Verify file export functionality is accessible
    Identify if the GoldenDB web interface, CLI tools, or API endpoints that support file export (such as exporting query results, reports, or database objects) are enabled and accessible to users or automated processes.
    Affected if File export features are enabled and accessible to users or external attackers
  4. Inspect exported files for DDE patterns
    Examine recently exported files from GoldenDB for suspicious patterns. Check exported files (CSV, Excel, text exports) for DDE formulas such as '=cmd|', '=MSGBOX', '=EXEC', or other dynamic data exchange expressions that could trigger automatic command execution when opened in spreadsheet applications.
    Affected if Exported files contain unvalidated DDE expressions that execute automatically on opening

Environment is affected if GoldenDB version is 6.1.03 through 6.1.03.10 or exactly 7.2.01.01, and the file export functionality is accessible to users or attackers who can inject DDE payloads into exported files.

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.

dbcve · scoped
Upgrade available Upgrade to 6.1.03.11 or later
Fixed in 6.1.03.11
Interim mitigation

Implement strict input validation and sanitization to prevent DDE expressions from being embedded in exported files; consider warning dialogs or disabling DDE auto-update features in generated files; educate users about risks of opening files from untrusted sources.

Recommended fix Moderate confidence

GoldenDB 6.1.03.11 or later for 6.x branch; version greater than 7.2.01.01 for 7.x branch

  1. 1. Identify the current GoldenDB version by checking the system information or using the database management interface.
  2. 2. For versions 6.1.03.x where x < 11, plan upgrade to version 6.1.03.11 or later.
  3. 3. For version 7.2.01.01, plan upgrade to a later version in the 7.x branch.
  4. 4. Backup all database configurations, schemas, and critical data before initiating the upgrade.
  5. 5. Consult ZTE GoldenDB support documentation (support.zte.com.cn) for version-specific upgrade procedures.
  6. 6. Execute the upgrade following the standard GoldenDB upgrade process for your deployment mode.
  7. 7. After upgrade, verify the DDE injection vulnerability is resolved by testing file download and import functionality.
  8. 8. Confirm all services are running correctly post-upgrade.
Caveat Database upgrades may introduce compatibility changes with existing client applications; test thoroughly in staging environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Zxcloud Goldendb Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
40.0 hours of engineering $6,960
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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