CVE-2025-4428
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 · uneditedRemote Code Execution in API component in Ivanti Endpoint Manager Mobile 12.5.0.0 and prior on unspecified platforms allows authenticated attackers to execute arbitrary code via crafted API requests.
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 · moderate confidenceAuthenticated remote code execution vulnerability in the API component of Ivanti Endpoint Manager Mobile 12.5.0.0 and prior allows attackers with valid credentials to send crafted API requests that result in arbitrary 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< 11.12.0.5>= 12.3.0.0, < 12.3.0.2>= 12.4.0.0, < 12.4.0.2= 12.5.0.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Ivanti Endpoint Manager Mobile versionLog into the admin console and navigate to System Settings > About, or check the version displayed on the login page. Alternatively, inspect the installation directory for a version file or check the response headers from the server.Affected if The installed version falls into any of these ranges: < 11.12.0.5; >= 12.3.0.0 and < 12.3.0.2; >= 12.4.0.0 and < 12.4.0.2; or exactly 12.5.0.0
-
Confirm the API component is exposedCheck if the /api endpoint is accessible on the EPMM server by making a GET request to https://<hostname>/api. Also review the server configuration or firewall rules to determine if API endpoints are reachable from the network.Affected if The API endpoint is accessible from a network where attackers could send requests
-
Verify if default or weak authentication credentials are in useReview user accounts configured in the EPMM admin console under Users or Administrators. Check if default credentials have not been changed or if there are accounts with excessive privileges.Affected if There are user accounts that may have been compromised or default credentials still active
-
Review API access logs for suspicious activityExamine the EPMM server logs, typically found in the logs directory or via the admin console, for API requests that include unusual parameters, repeated authentication attempts, or requests to unexpected endpoints.Affected if Logs show API requests with suspicious payloads, especially from unfamiliar IP addresses or using valid user accounts
A user is affected if their Ivanti Endpoint Manager Mobile version is in the vulnerable ranges and the API component is network-accessible with valid user credentials available for exploitation.
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 · scoped11.12.0.512.3.0.212.4.0.2
Upgrade to a patched version of Ivanti Endpoint Manager Mobile. If immediate patching is not possible, restrict network access to the API endpoints and implement additional authentication controls beyond default credentials.
11.12.0.5 (11.x), 12.3.0.2 (12.3.x), 12.4.0.2 (12.4.x), or 12.5.0.1 (12.5.x) - choose the appropriate fixed version for your current branch
- 1. Identify the current version of Ivanti Endpoint Manager Mobile by checking the product's About or version information page.
- 2. Determine which version branch your current installation belongs to (11.x, 12.3.x, 12.4.x, or 12.5.x).
- 3. Download the appropriate fixed version for your branch from the official Ivanti download portal or support site: for 11.x branch use 11.12.0.5 or later, for 12.3.x use 12.3.0.2 or later, for 12.4.x use 12.4.0.2 or later, for 12.5.x use 12.5.0.1 or later.
- 4. Review Ivanti upgrade documentation and release notes for your specific version branch before upgrading.
- 5. Create a full backup of the current Endpoint Manager Mobile installation and database.
- 6. Test the upgrade in a staging environment before deploying to production.
- 7. Apply the upgrade during a planned maintenance window following Ivanti's official upgrade procedures.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-4428 — 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-4428 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