Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Arbitrary File Write and Potential RCE in Ivanti Endpoint Manager

IdentifiersCVE-2025-13659CWE-913· Improper Control of…

CVE-2025-13659 is a high-severity vulnerability in Ivanti Endpoint Manager (EPM) prior to version 2024 SU4 SR1. The issue is described by Ivanti as improper control of dynamically managed code resources and allows a remote, unauthenticated attacker to write arbitrary files on the EPM server. Supporting reporting further associates the flaw with the broader 'SOAPwn' class of legacy .NET Framework SOAP client issues, in which attacker-influenced SOAP/WSDL handling can be abused to redirect writes and inject payloads, including via namespace payload injection. In the Ivanti EPM context, successful exploitation can result in arbitrary file creation on the server and may be escalated to remote code execution. The vendor states that user interaction is required for exploitation.

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 an unauthenticated remote attacker to write arbitrary files to the Ivanti EPM server. If the attacker can place executable content in a reachable or interpreted location, this can lead to remote code execution on the server. In practical terms, this may enable deployment of webshells or malicious scripts, compromise of the EPM application host, and abuse of EPM's privileged management role for follow-on actions such as endpoint compromise, lateral movement, persistence, and broader enterprise impact.

Mitigation

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

Primary mitigation is prompt patching. Until updates can be applied, reduce exposure by ensuring Ivanti EPM is not internet-facing, restricting access to management interfaces to trusted administrative networks, and implementing network segmentation around the EPM server. Because available reporting indicates exploitation may involve untrusted core server connections or untrusted SOAP/WSDL-related inputs, administrators should avoid connecting to untrusted core servers and should not import or process untrusted configuration or service-description data. Additional defensive measures include monitoring the EPM server for unexpected file creation in web-accessible or executable paths and reviewing any application components that consume attacker-controlled SOAP/WSDL content.

Remediation

Patch, then assume compromise.

Upgrade Ivanti Endpoint Manager to version 2024 SU4 SR1 or later. Ivanti states that 2024 SU4 SR1 remediates CVE-2025-13659. Organizations running affected earlier releases should apply the vendor-supplied update immediately through the Ivanti License System. If the environment is on an unsupported branch, such as EPM 2022 after end of support, migration to a supported version is required because unsupported versions will not receive security fixes.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

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 Managerapplication

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 evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

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 activity8

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