CVE-2025-6771
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 · uneditedOS command injection in Ivanti Endpoint Manager Mobile (EPMM) before version 12.5.0.2,12.4.0.3 and 12.3.0.3 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 confidenceOS command injection vulnerability in Ivanti Endpoint Manager Mobile allows remote authenticated attackers with high privileges to execute arbitrary OS commands, leading to remote code execution. The flaw exists in versions prior to 12.5.0.2, 12.4.0.3, and 12.3.0.3.
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< 12.3.0.3>= 12.4.0.0, < 12.4.0.3>= 12.5.0.0, < 12.5.0.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Ivanti Endpoint Manager Mobile is installedCheck for the presence of Ivanti Endpoint Manager Mobile services or binaries on the server, typically in the installation directory (e.g., C:\Program Files\Ivanti or /opt/ivanti). Look for processes named 'EPMM' or similar.Affected if The product is present on the system
-
Determine installed versionLocate the version information in the product's about page, configuration file, or by running the product's version command. Common locations include the admin web interface (usually under Help > About) or a version file in the installation directory.Affected if The installed 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
-
Verify admin/web interface is accessibleCheck if the Ivanti EPMM web console is exposed and accessible (typically on ports 8080, 8443, or 443). Confirm the administrative portal is reachable from network locations.Affected if The web administration interface is exposed and accessible
-
Review administrative accountsAudit the list of administrative users configured in Ivanti EPMM. Check for any unauthorized or unexpected high-privilege accounts that may indicate compromise.Affected if There are high-privilege accounts that were not created by trusted administrators
-
Inspect for signs of exploitationReview server logs, especially web access logs and command audit logs, for suspicious commands or unexpected API calls that may indicate exploitation attempts. Look for unusual patterns in command execution logs.Affected if Unexpected commands, shell invocations, or suspicious API calls appear in logs
The environment is affected if Ivanti Endpoint Manager Mobile is installed and the installed version is one of the vulnerable releases (< 12.3.0.3, 12.4.0.0-12.4.0.2, or 12.5.0.0-12.5.0.1) with the administrative interface accessible.
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 · scoped12.3.0.312.4.0.312.5.0.2
Upgrade Ivanti Endpoint Manager Mobile to version 12.5.0.2, 12.4.0.3, 12.3.0.3 or later. Restrict administrative access to trusted users only until the patch is applied.
12.5.0.2 (or 12.4.0.3 or 12.3.0.3 depending on your current version branch)
- 1. Back up the current Ivanti Endpoint Manager Mobile (EPMM) installation and all data before proceeding with the upgrade
- 2. Review the official Ivanti upgrade documentation and release notes for EPMM on forums.ivanti.com or the Ivanti knowledge base
- 3. Determine your current EPMM version to select the appropriate upgrade path
- 4. Upgrade to EPMM version 12.5.0.2 (recommended for latest features) OR version 12.4.0.3 OR version 12.3.0.3, depending on your current major version branch
- 5. Follow the standard upgrade procedure provided in Ivanti documentation
- 6. After upgrade, verify the EPMM web interface is accessible and services are running
- 7. Test that core EPMM functions (device enrollment, policy deployment, device management) are operating normally
- 8. Confirm the version number reflects the upgrade in the EPMM admin console
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6771 — 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-6771 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