CVE-2025-4427
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 · uneditedAn authentication bypass in the API component of Ivanti Endpoint Manager Mobile 12.5.0.0 and prior allows attackers to access protected resources without proper credentials via the API.
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 confidenceThis is an authentication bypass vulnerability in the API component of Ivanti Endpoint Manager Mobile (EPMM) version 12.5.0.0 and prior. The flaw allows unauthenticated attackers to bypass authentication mechanisms and access protected API resources without proper credentials, potentially exposing sensitive data or enabling privilege escalation.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 installed version of Ivanti Endpoint Manager MobileAccess the admin console or system information page. Typically found under Help > About or Settings > System Information. If console access is unavailable, check installation directories or version configuration files for a version string.Affected if The installed version matches 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 equals 12.5.0.0
-
Confirm the API component is accessibleDetermine if the API component is exposed. This typically involves checking the service configuration, web server settings, or network listener configuration for the Mobile component. Look for API endpoint availability on ports commonly used by the product (often ports 8080, 8443, or 443).Affected if The API component is enabled and reachable on the network
-
Verify API is exposed to untrusted networksReview firewall rules, network segmentation, and access control lists to determine if the API endpoint is accessible from outside the trusted internal network or from unauthenticated networks.Affected if The API component can be reached from untrusted networks or the internet without VPN or authentication proxy
-
Check for suspicious API access patternsReview API access logs, authentication logs, and audit trails for requests to API endpoints that lack proper authentication headers, session tokens, or credentials. Look for successful responses to protected API calls from unexpected sources.Affected if Logs show API requests accessing protected resources without valid authentication or from unrecognized sources
You are affected if the installed version falls within the affected version ranges AND the API component is enabled and network-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 · scoped11.12.0.512.3.0.212.4.0.2
Upgrade Ivanti Endpoint Manager Mobile to the patched version as specified in vendor advisories. If immediate patching is not possible, implement network segmentation and firewall rules to restrict unauthenticated access to the API endpoints.
11.12.0.5+ (11.x), 12.3.0.2+ (12.3.x), 12.4.0.2+ (12.4.x), 12.5.0.1+ (12.5.x)
- Identify the current installed version of Ivanti Endpoint Manager Mobile
- For version 11.x: upgrade to version 11.12.0.5 or later
- For version 12.3.x: upgrade to version 12.3.0.2 or later
- For version 12.4.x: upgrade to version 12.4.0.2 or later
- For version 12.5.0.0: upgrade to version 12.5.0.1 or later
- After upgrading, verify the authentication bypass is remediated by testing API access with invalid credentials
- Review and apply any additional security hardening recommendations from Ivanti documentation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-4427 — 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-4427 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