Ivanti Endpoint Manager Mobile (EPMM) Code Injection Vulnerability
Exploited since 2025-05-19. 2 of 8 rule sources name it; Cloudflare blocks by default.
Remote 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.
Edge coverage
Claimed by vendorsAsk Vigil
AI · answers from this pageWorkers AI (Llama 3.3). Can be wrong: check the cited source.
Severity, decoded
CVSS 3.1Exploitable over the network, with high privileges and no user interaction, leading to full loss of confidentiality, integrity and availability.
How the score is built
- Attack vectorAn attacker can reach it over the internet; no access to your network needed.Network
- Attack complexityNo special conditions are needed; the attack works reliably.Low
- Privileges requiredThe attacker needs an administrator-level account.High
- User interactionNo one has to click or open anything; the attack works on its own.None
- ScopeThe damage stays within the vulnerable component.Unchanged
- Confidentiality impactAn attacker can read all data the affected component holds, or the most sensitive parts of it.High
- Integrity impactAn attacker can change any data or files the affected component protects.High
- Availability impactAn attacker can take the component down completely or keep it from serving anyone.High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HAttackers are exploiting this in the wild.
Attackers can script the attack end to end and hit many targets at once.
A successful attack gives full control over the affected software or all of its data.
Public exploits
1 found- MetasploitIvanti EPMM Authentication Bypass for Expression Language Remote Code Execution2025-05-13 · exploit · rank Excellent · has check
Links are to third-party code: never run it outside an isolated lab.
Timeline
- 2025-05-13CVE publishedCVE List
- 2025-05-13Metasploit module publishedIvanti EPMM Authentication Bypass for Expression Language Remote Code Execution
- 2025-05-19Added to CISA KEVConfirmed exploitation in the wild
- 2025-05-27Cloudflare ships a ruleIvanti EPMM - Auth Bypass - CVE:CVE-2025-4428, CVE:CVE-2025-4427
- 2025-06-30F5 ships a ruleIvanti EPMM Expression Injection
Vendor statements
QuotedCloudflareWAF Managed Rules
First rule 2025-05-27, 14 days after the CVE was published.
Ivanti EPMM - Auth Bypass - CVE:CVE-2025-4428, CVE:CVE-2025-4427. Previous action: Log. New action: Block. This is a New Detection
AWSAWS WAF Managed Rules
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. AWS often describes a vulnerability without naming its CVE (for example "Log4j"). We count only entries that name the CVE, so AWS coverage is understated.
Microsoft AzureFront Door and Application Gateway WAF (DRS)
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. The rule tables name CVEs but carry no dates, so Azure is left out of every time-to-rule figure.
Google CloudCloud Armor preconfigured WAF rules
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. Google names few CVEs: the release notes start in May 2024 and the rules reference lists CVEs without dates. Its cve-canary rules are opt-in.
FastlyNext-Gen WAF virtual patches
The CVE predates the oldest entry in this vendor's public feed, so a rule may exist that we cannot see.
F5Attack signatures (Distributed Cloud WAF)
First rule 2025-06-30, 48 days after the CVE was published.
Added: signature 200204016 "Ivanti EPMM Expression Injection" (Server Side Code Injection, risk High), systems: Other Web Server. References: CVE-2025-4428, CVE-2025-4427.
Added: signature 200204022 "Ivanti EPMM Expression Injection (2)" (Server Side Code Injection, risk High), systems: Other Web Server. References: CVE-2025-4428, CVE-2025-4427.
AkamaiApp & API Protector (Adaptive Security Engine)
This vendor publishes no machine-readable rule changelog we can check.
OWASP CRSCore Rule Set (open source, used inside many WAFs)
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. CRS rarely names CVEs: it relies on generic detections. Our own lab measures what it actually blocks.
Social
No posts seen yet on X, Bluesky, Mastodon, Hacker News or GitHub.