LiveActive security incident?Get immediate response
CVE Record

CVE-2025-4427: Authentication Bypass

An 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.

MediumCVSS 5.3Known exploitedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Ivanti Endpoint Manager Mobile has an API authentication bypass that can let an unauthenticated attacker reach protected resources. The technical severity is medium, but CISA lists it in KEV, meaning known exploitation exists. Organizations using exposed Ivanti EPMM should treat this as urgent despite the CVSS score.

Executive priority

Prioritize as a near-term remediation item for any exposed EPMM deployment. Although the base score is medium, CISA KEV status means real-world exploitation has been observed, changing the business risk profile.

Technical view

CVE-2025-4427 is a CWE-288 authentication bypass in the EPMM API. The CVSS 3.1 vector is network-reachable, low complexity, no privileges, no user interaction, with limited confidentiality impact. The source bundle identifies EPMM 12.5.0.0 and prior, while its affected version field is inconsistent.

Likely exposure

Exposure is most relevant where Ivanti Endpoint Manager Mobile API endpoints are reachable from untrusted networks. Internet-facing management infrastructure increases urgency, especially because CISA KEV indicates exploitation in the wild.

Exploitation context

Active exploitation is supported by the CISA Known Exploited Vulnerabilities listing. The provided sources do not describe attacker tooling, affected deployment patterns, or whether exploitation requires chaining with another flaw.

Researcher notes

The source data has a version inconsistency: the description says 12.5.0.0 and prior, while the affected list names 12.5.0.1. Validate directly against Ivanti’s advisory before scoping remediation or writing detections.

Mitigation direction

  • Review Ivanti’s advisory for the vendor-approved fix or workaround.
  • Prioritize remediation for internet-facing EPMM instances.
  • Restrict API access to trusted networks where operationally possible.
  • Monitor Ivanti and CISA updates for corrected affected-version details.
  • Do not rely on CVSS alone because KEV raises operational urgency.

Validation and detection

  • Inventory all Ivanti Endpoint Manager Mobile deployments and versions.
  • Confirm whether API endpoints are externally reachable.
  • Check whether the instance matches Ivanti’s advisory scope.
  • Review access logs for unauthenticated API access anomalies.
  • Verify remediation status against current Ivanti guidance.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-288: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-4427 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2025-4427Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
IvantiEndpoint Manager Mobile12.5.0.1affected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-288 · source CWE mapping

Authentication Bypass Using an Alternate Path or Channel

Authentication Bypass Using an Alternate Path or Channel represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.