Security Resilience

CVE-2025-46576

Zte Zxcloud Goldendb 6.1.03.09 … 7.2.01.01

Published
27 April 2025
Modified
17 June 2026
Patch / advisory
CVSS Score v3.1 5.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
EPSS Score 0.0029 20th percentile
Risk Priority 43 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-46576 is a medium-severity Improper Privilege Management (CWE-269) vulnerability in Zte Zxcloud Goldendb. Its CVSS base score is 5.4 (Medium).

Operationally, ranked at the 20th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-2 (Account Management) and AC-24 (Access Control Decisions) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

There is a Permission Management and Access Control vulnerability in the GoldenDB database product. Attackers can manipulate requests to bypass privilege restrictions and delete content.

CWE(s)

Related Threats

CVEs Like This One

CVE-2025-46577Same product: Zte Zxcloud Goldendb
CVE-2025-46574Same product: Zte Zxcloud Goldendb
CVE-2025-46578Same product: Zte Zxcloud Goldendb
CVE-2025-46580Same product: Zte Zxcloud Goldendb
CVE-2025-46575Same product: Zte Zxcloud Goldendb
CVE-2025-46579Same product: Zte Zxcloud Goldendb
CVE-2023-41784Same vendor: Zte
CVE-2024-22069Same vendor: Zte
CVE-2025-26703Same vendor: Zte
CVE-2025-26704Same vendor: Zte

Affected Assets

zte
zxcloud goldendb
6.1.03.09, 6.1.03.10, 7.2.01.01

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Account management directly governs assignment and tracking of privileges so proper implementation stops the weakness from being introduced.

Requiring explicit access-control decisions ensures privileges are evaluated rather than assumed or omitted.

Access enforcement applies the correct privilege checks at every request, structurally preventing unintended spheres of control.

Separation of duties constrains how privileges may be assigned, reducing the chance of overly broad actor control.

Least privilege is the direct countermeasure to improper privilege management; implementing it eliminates the root cause.

Binding security attributes to subjects/objects supplies the mechanism needed to track and enforce privileges correctly.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

blocks

A.5.15 directly mandates determining access requirements, defining/enforcing topic-specific access control policy, assigning rights/restrictions by entity/role, consistency with classification, need-to-know, privileged access restrictions, segregation, formal authorization, and dynamic rules — which stops most improper privilege management from being exploitable; bounded remainder is flawed implementation of those rules (e.g. incorrect mapping or enforcement bugs).

blocks

A.5.18 directly governs the provisioning, review, modification and timely revocation of access rights (including for role changes, termination and privilege levels), which stops most improper privilege spheres from being exploitable even if the assignment flaw exists; the bounded remainder is flaws in the underlying enforcement mechanism itself (e.g. AC-3/A.8.3)

blocks

A.8.2 directly controls the identification, allocation, review, expiry, temporary use, and separation of privileged rights per policy, which prevents most improper privilege management (CWE-269) by design; the bounded remainder is flawed tracking/checking logic inside the product's own enforcement code (the AC-3 slice of 269).

blocks

A.8.3 directly restricts access per policies (config mechanisms, per-user/group rights, isolation, dynamic techniques, auth/credential enforcement), which stops exploitation of most improper privilege management cases even if the assignment/tracking flaw remains; named remainder exists for non-access-control privilege errors (e.g. pure assignment bugs outside enforcement).

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

References