dbcve.org
Endpoint Manager MobileApplication · Ivanti

CVE-2025-6770

HIGH · 7.2 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 12.3.0.3 / 12.4.0.3 or later.
See remediation →
78/100
Remediation priority · High
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
OS command injection in Ivanti Endpoint Manager Mobile (EPMM) before version 12.5.0.2 allows a remote authenticated attacker with high privileges to achieve remote code execution

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

OS command injection vulnerability in Ivanti Endpoint Manager Mobile (EPMM) allows a remote authenticated attacker with high privileges to execute arbitrary OS commands, achieving remote code execution. The vulnerability affects versions prior to 12.5.0.2.

MitigationUpgrade Ivanti Endpoint Manager Mobile to version 12.5.0.2 or later to remediate this vulnerability.

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
Endpoint Manager MobileApplication
Affected:< 12.3.0.3>= 12.4.0.0, < 12.4.0.3>= 12.5.0.0, < 12.5.0.2

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

CVSS:3.1/AV:N/AC:L/PR:H/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. Identify Ivanti EPMM version via web interface
    Log into the Ivanti Endpoint Manager Mobile admin console and navigate to the About or System Information page, typically found under Settings > System > About or /help/about. Record the displayed version number.
    Affected if The displayed version falls within < 12.3.0.3, >= 12.4.0.0 and < 12.4.0.3, or >= 12.5.0.0 and < 12.5.0.2.
  2. Identify Ivanti EPMM version via API endpoint
    Send an authenticated GET request to the EPMM API endpoint such as /api/v1/system/info or /api/v1/config/version. Parse the JSON response for the 'version' or 'productVersion' field.
    Affected if The reported version falls within any of the affected ranges listed above.
  3. Identify Ivanti EPMM version via local file inspection
    On the EPMM server, locate the version file typically found in the installation directory. Common paths include /opt/epmm/version, /opt/mobileiron/core/version.txt, or check the WAR file metadata in the application deployment directory.
    Affected if The version file contains a version number within the affected ranges.
  4. Verify if remote API access is enabled
    Check the EPMM configuration for exposed API endpoints. This can be done by reviewing the server.xml or reverse proxy configuration to confirm that API endpoints such as /api/ are accessible from the network.
    Affected if The API is exposed and the EPMM version is within the affected ranges, indicating the command injection vector is reachable.

The environment is affected if the installed Ivanti Endpoint Manager Mobile version is less than 12.3.0.3, between 12.4.0.0 and 12.4.0.3 exclusive, or between 12.5.0.0 and 12.5.0.2 exclusive.

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 12.3.0.3 / 12.4.0.3 / 12.5.0.2 or later
Fixed in 12.3.0.312.4.0.312.5.0.2
Interim mitigation

Upgrade Ivanti Endpoint Manager Mobile to version 12.5.0.2 or later to remediate this vulnerability.

Recommended fix High confidence

12.5.0.2 or later

  1. Verify current EPMM version by navigating to Settings > System > About in the management console
  2. Review Ivanti product documentation and release notes for version 12.5.0.2 upgrade requirements
  3. Create a complete backup of the EPMM database and configuration
  4. Schedule a maintenance window to minimize business impact
  5. Download the EPMM version 12.5.0.2 (or later) installer from the Ivanti download portal
  6. Stop all EPMM services before upgrade installation
  7. Run the installer with appropriate administrative privileges
  8. Follow the on-screen upgrade wizard prompts

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

Fix this in Endpoint Manager Mobile Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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