Skip to main content
Mallory
HighCISA KEVExploited in the wildPublic exploit

Ivanti Endpoint Manager Mobile SpEL Injection RCE

IdentifiersCVE-2025-4428CWE-94· Improper Control of Generation of…

CVE-2025-4428 is a remote code execution vulnerability in the API component of Ivanti Endpoint Manager Mobile (EPMM) affecting version 12.5.0.0 and earlier. The available supporting content indicates the flaw is a Spring Expression Language (SpEL) injection in the format parameter of the /api/v2/featureusage endpoint family, allowing crafted API requests to be interpreted as executable expressions. Multiple sources in the content state that this issue was actively exploited in the wild in 2025. While one description characterizes the flaw as exploitable by an authenticated attacker, the broader supporting context consistently indicates that CVE-2025-4428 was commonly chained with CVE-2025-4427, an authentication bypass, to achieve unauthenticated remote code execution against internet-facing EPMM appliances.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows arbitrary code execution on the vulnerable Ivanti EPMM server. In observed campaigns described in the content, attackers used the CVE-2025-4427/CVE-2025-4428 chain to compromise exposed EPMM instances, extract data from backend MySQL databases, obtain LDAP user details and Office 365 tokens, and use stolen credentials for internal lateral movement. Additional reporting in the content indicates compromise of EPMM can expose sensitive mobile-management data and potentially enable abuse of the platform's administrative control over enrolled devices.

Mitigation

If you can’t patch tonight, do this now.

Restrict exposure of EPMM administrative and API interfaces to trusted networks only, including use of API access control lists as referenced in the content. Remove or tightly limit internet exposure of EPMM appliances wherever possible. Monitor relevant web and Apache access logs for suspicious requests to featureusage-related API endpoints and investigate signs of exploitation. Given reports of active exploitation and post-compromise credential/token theft, rotate potentially exposed credentials and tokens, review backend database access, and perform incident response on systems that were internet-facing and unpatched during the exploitation window.

Remediation

Patch, then assume compromise.

Apply Ivanti's vendor-provided fixes immediately. The content states Ivanti released patches on May 13, 2025 for affected EPMM branches, including remediation for versions 11.12.0.x before 11.12.0.5, 12.3.0.x before 12.3.0.2, 12.4.0.x before 12.4.0.2, and 12.5.0.x before 12.5.0.1. If patching cannot be completed immediately, apply Ivanti's published workaround RPM and follow the vendor security advisory for the correct upgrade path. Because exploitation was active in the wild and public PoC material became available shortly after disclosure, exposed systems should be investigated for compromise even after patching.
PUBLIC EXPLOITS

Exploits

1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (2 hidden).

VALID 1 / 3 TOTALView more in app
CVE-2025-4428MaturityPoCVerified exploit

This repository provides an operational exploit and detection tool for CVE-2025-4427 and CVE-2025-4428, targeting Ivanti Endpoint Manager Mobile (EPMM). The main exploit is implemented in 'CVE-2025-4428.py', a Python script that allows unauthenticated remote code execution by exploiting a Server-Side Template Injection (SSTI) vulnerability in a Java bean validator. The exploit works by sending a crafted HTTP GET request to vulnerable endpoints (such as '/api/v2/featureusage' and '/api/v2/featureusage_history') with a malicious 'format' parameter that triggers arbitrary command execution on the server. The script supports custom command execution, proxying, output redirection, and multi-shell support (bash/sh). The YAML file ('CVE-2025-4427.yaml') provides a nuclei-compatible detection template for automated scanning. The repository is well-structured, with clear documentation and operational exploit code, and is suitable for both detection and exploitation of the targeted vulnerabilities.

xie-22Disclosed May 16, 2025pythonyamlnetwork
EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
IvantiEndpoint Manager Mobileapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence3

Every observed campaign linking this CVE to a named adversary.

Associated malware3

Malware families riding this exploit, with evidence and IOCs.

Detection signatures1

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity120

Community discussion across Reddit, Mastodon, and other social sources.