dbcve.org
CloudstackApplication · Apache

CVE-2025-47713

HIGH · 8.8 CVSS v3.1 Published 2025-06-10
Fix available
A fix is available. Upgrade to 4.19.3.0 / 4.20.1.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
A privilege escalation vulnerability exists in Apache CloudStack versions 4.10.0.0 through 4.20.0.0 where a malicious Domain Admin user in the ROOT domain can reset the password of user-accounts of Admin role type. This operation is not appropriately restricted and allows the attacker to assume control over higher-privileged user-accounts. A malicious Domain Admin attacker can impersonate an Admin user-account and gain access to sensitive APIs and resources that could result in the compromise of resource integrity and confidentiality, data loss, denial of service, and availability of infrastructure managed by CloudStack. Users are recommended to upgrade to Apache CloudStack 4.19.3.0 or 4.20.1.0, which fixes the issue with the following: * Strict validation on Role Type hierarchy: the caller's user-account role must be equal to or higher than the target user-account's role. * API privilege comparison: the caller must possess all privileges of the user they are operating on. * Two new domain-level settings (restricted to the default Admin):  - role.types.allowed.for.operations.on.accounts.of.same.role.type: Defines which role types are allowed to act on users of the same role type. Default: "Admin, DomainAdmin, ResourceAdmin".    - allow.operations.on.users.in.same.account: Allows/disallows user operations within the same account. Default: true.

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 confidence

Apache CloudStack versions 4.10.0.0 through 4.20.0.0 contain a privilege escalation flaw where Domain Admin users in the ROOT domain can reset passwords of higher-privileged Admin role accounts. The password reset API lacks proper role hierarchy validation, allowing a malicious Domain Admin to impersonate Admin users and access sensitive infrastructure management APIs.

MitigationUpgrade to Apache CloudStack 4.19.3.0 or 4.20.1.0 which implements strict role type hierarchy validation, API privilege comparison, and configurable domain-level settings to restrict password reset operations based on caller/target role relationships.

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
CloudstackApplication
Affected:>= 4.10.0.0, < 4.19.3.0>= 4.20.0.0, < 4.20.1.0

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

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine CloudStack management server version
    Run 'cloudstack-sysvmadm --version' or check the RPM/DEB package version (rpm -q cloudstack-management), or query the API endpoint GET /client/api?command=listVersions
    Affected if Version falls within 4.10.0.0 through 4.19.3.0, or 4.20.0.0 through 4.20.1.0 (i.e., less than 4.19.3.0 or less than 4.20.1.0)
  2. Identify Domain Admin users in ROOT domain
    Use the CloudStack API command 'listUsers' with domainid=ROOT (or the UI/CLI) and filter for users with role=DomainAdmin or type=DOMAIN_ADMIN
    Affected if Any user account with Domain Admin role exists within the ROOT domain (domainid=ROOT)
  3. Verify if password reset API accepts Domain Admin input for higher roles
    As a test (in a non-production environment), authenticate as a Domain Admin in ROOT domain and call the resetPassword API targeting an Admin user account, observing whether the API call succeeds without permission denied error
    Affected if The API call returns a success response (new password or reset confirmation) rather than an authorization error, indicating the vulnerability is present

You are affected if your CloudStack version is below 4.19.3.0 or below 4.20.1.0 AND you have Domain Admin users defined in the ROOT domain who can successfully reset Admin user passwords via the API.

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 4.19.3.0 / 4.20.1.0 or later
Fixed in 4.19.3.04.20.1.0
Interim mitigation

Upgrade to Apache CloudStack 4.19.3.0 or 4.20.1.0 which implements strict role type hierarchy validation, API privilege comparison, and configurable domain-level settings to restrict password reset operations based on caller/target role relationships.

Recommended fix High confidence

Apache CloudStack 4.19.3.0 or 4.20.1.0

  1. 1. Perform a complete backup of the CloudStack database and configuration files before starting the upgrade process.
  2. 2. Stop all CloudStack services (management server, agents) following the standard maintenance procedure.
  3. 3. Upgrade the CloudStack management server to version 4.19.3.0 (for 4.x line) or 4.20.1.0 (for 4.20.x line) using the official upgrade documentation.
  4. 4. Run the database migration scripts included in the upgrade to apply schema changes for the new privilege validation.
  5. 5. Restart CloudStack services in the correct order (management server first, then agents).
  6. 6. Verify the upgrade by logging in as a Domain Admin and confirming that password reset operations on Admin role accounts are now properly restricted.
  7. 7. Test that the new role type hierarchy validation is enforced by attempting (and failing) to perform operations on higher-privileged users.
Caveat New security validations may restrict existing automation scripts that relied on the vulnerable cross-role password reset behavior; test existing integrations after upgrade

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

Fix this in Cloudstack Scoped from the published advisory
  • Consultation6.0 h
  • Implementation20.0 h
  • Testing14.0 h
  • Review / QA6.0 h
46.0 hours of engineering $7,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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