CVE-2025-10242
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 the admin panel of Ivanti EPMM before version 12.6.0.2, 12.5.0.4, and 12.4.0.4 allows a remote authenticated attacker with admin 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 the admin panel of Ivanti EPMM allows authenticated attackers with admin privileges to execute arbitrary operating system commands by injecting malicious commands through unsanitized input fields, leading to full remote code execution on the affected system.
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.4.0.4>= 12.5.0.0, < 12.5.0.4>= 12.6.0.0, < 12.6.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.
-
Determine installed Ivanti EPMM versionAccess the admin console and navigate to System Settings > About, or check the installer file properties on the server. Alternatively, examine the application banner or release notes provided during startup.Affected if The installed version falls outside the fixed versions: not 12.4.0.4 or later in the 12.4.x branch, not 12.5.0.4 or later in the 12.5.x branch, and not 12.6.0.2 or later in the 12.6.x branch.
-
Verify admin panel accessibilityConfirm the Ivanti EPMM admin interface is reachable over the network by accessing the login URL (typically /admin or /MHE/jsp/login.jsp on the server hostname). Check firewall rules and reverse proxy configurations.Affected if The admin panel is exposed to untrusted networks, increasing the likelihood of credential compromise and exploit attempts.
-
Identify admin-level user accountsIn the admin console, navigate to Users or Administrators to list accounts with administrative privileges. Check for any unauthorized or unexpected admin accounts.Affected if There are admin accounts beyond the expected minimum, or accounts exist that were not created by known administrators, indicating potential credential theft or unauthorized access.
-
Inspect for suspicious scheduled tasks or processesOn the Ivanti EPMM server, review the task scheduler or running services for commands or scripts that were not authored by your organization. Use operating system utilities such as Task Scheduler on Windows or cron on Linux.Affected if Unexpected scheduled tasks, services, or processes are present, particularly those executing external network calls or spawning shells.
A user is affected if their Ivanti EPMM version is below the fixed releases (12.4.0.4, 12.5.0.4, or 12.6.0.2) AND the admin panel is accessible to attackers who could obtain admin credentials.
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.4.0.412.5.0.412.6.0.2
Upgrade Ivanti EPMM to version 12.6.0.2, 12.5.0.4, or 12.4.0.4 or later to patch the command injection vulnerability. Restrict admin panel access to trusted users and monitor for suspicious activity until patching is complete.
12.6.0.2 (or 12.5.0.4 or 12.4.0.4 depending on your release branch)
- 1. Identify current Ivanti EPMM version by logging into the admin panel and checking the version information page
- 2. Take a complete backup of the Ivanti EPMM configuration and database, following your organization's backup procedures
- 3. Download the appropriate fixed version from the Ivanti Support Portal (https://forums.ivanti.com): 12.4.0.4, 12.5.0.4, or 12.6.0.2
- 4. Review Ivanti's upgrade documentation and release notes for the target version before proceeding
- 5. Schedule a maintenance window as upgrades require downtime
- 6. Upload the upgrade package through the admin panel or deploy via your standard upgrade method
- 7. After upgrade completes, verify the new version number in the admin panel
- 8. Test critical functionality to ensure the upgrade was successful
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10242 — 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-10242 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