dbcve.org
Endpoint ManagerApplication · Ivanti

CVE-2025-9712

HIGH · 8.8 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to 2022 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Insufficient filename validation in Ivanti Endpoint Manager before 2024 SU3 SR1 and 2022 SU8 SR2 allows a remote unauthenticated attacker to achieve remote code execution. User interaction is required.

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 · high confidence

Insufficient filename validation in Ivanti Endpoint Manager prior to versions 2024 SU3 SR1 and 2022 SU8 SR2 allows remote unauthenticated attackers to achieve remote code execution through a vulnerability that requires user interaction to exploit.

MitigationApply the appropriate security update (2024 SU3 SR1 or 2022 SU8 SR2) to Ivanti Endpoint Manager. As user interaction is required, also consider user awareness training and network segmentation to reduce attack surface.

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
Endpoint ManagerApplication
Affected:< 2022= 2022= 2024

CVSS 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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Ivanti Endpoint Manager version
    Locate the version information in the product's about page, registry, or admin console. Common locations: Help > About in the console, or check registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\Ivanti\EndpointManager
    Affected if The installed version falls within < 2022, = 2022, or = 2024 (prior to SU3 SR1) or = 2022 prior to SU8 SR2
  2. Confirm version is not patched
    Compare your installed version against the fixed releases: 2024 SU3 SR1 or 2022 SU8 SR2. If your version is older than these releases, you are in the affected range
    Affected if Version is earlier than 2024 SU3 SR1 (for 2024 releases) or earlier than 2022 SU8 SR2 (for 2022 releases)
  3. Verify file upload or import functionality is accessible
    Check if the Ivanti Endpoint Manager console or API endpoints that handle file uploads, package imports, or agent updates are exposed to network access. Review IIS or web server bindings and firewall rules
    Affected if File handling endpoints are exposed to unauthenticated or low-privilege network access
  4. Review for suspicious file operations in logs
    Examine Ivanti Endpoint Manager logs (typically in C:\Program Files\Ivanti\Endpoint Manager\Logs or similar) for unusual filename patterns, path traversal attempts, or unexpected file creation events
    Affected if Logs show anomalous filename patterns or unexpected file writes that may indicate exploitation attempts

You are affected if Ivanti Endpoint Manager is running version 2022 (any release), 2024 (prior to SU3 SR1), or any version older than 2022, and the file handling functionality is network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2022 or later
Fixed in 2022
Interim mitigation

Apply the appropriate security update (2024 SU3 SR1 or 2022 SU8 SR2) to Ivanti Endpoint Manager. As user interaction is required, also consider user awareness training and network segmentation to reduce attack surface.

Recommended fix Moderate confidence

2024 SU3 SR1 (or later) / 2022 SU8 SR2 (or later)

  1. Download the latest Ivanti Endpoint Manager security update from the official Ivanti support portal or your licensed distribution channel
  2. Review the upgrade documentation and release notes for version 2024 SU3 SR1 or 2022 SU8 SR2
  3. Ensure you have a complete backup of the Ivanti Endpoint Manager database and configuration
  4. Test the upgrade in a non-production environment before deploying to production
  5. Execute the upgrade installer following the standard Ivanti upgrade procedure
  6. Verify the upgrade completed successfully by checking the version in the admin console
  7. Confirm that the filename validation vulnerability is resolved by reviewing release notes
Caveat Standard upgrade risks apply - test in staging first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Endpoint Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-9712 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-9712 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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