dbcve.org
IgnitionApplication · Inductiveautomation

CVE-2025-13913

MEDIUM · 6.8 CVSS v3.1 Published 2026-03-12
Fix available
A fix is available. Upgrade to 8.3.0 or later.
See remediation →
70/100
Remediation priority · Elevated
Zero-click

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
A privileged Ignition user, intentionally or otherwise, imports an external file with a specially crafted payload, which executes embedded malicious code.

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

This is a code execution vulnerability in Ignition (SCADA/HMI platform) where a privileged user can import an external file containing a specially crafted payload. The imported file contains embedded malicious code that executes upon import, leading to arbitrary code execution on the system.

MitigationRestrict file import permissions to only trusted administrators, implement strict file validation and sandboxing for imported files, and monitor/audit file import activities for suspicious behavior.

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
IgnitionApplication
Affected:< 8.3.0

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
Adjacent
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:H/UI:N/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. Check Ignition installation version
    Navigate to the Ignition Gateway web interface, then go to Status > Summary or Help > About to view the installed version number. Alternatively, check the installation directory for a version file or check the Gateway's startup logs.
    Affected if The installed version is any release prior to 8.3.0 (versions 8.2.x, 8.1.x, 8.0.x, or earlier)
  2. Verify file import functionality is accessible
    In the Ignition Gateway, navigate to Configure > System > Configuration > Files or similar file management section. Check if the file import/upload feature is available to any user role.
    Affected if File import capability is enabled and accessible to privileged users (not disabled or restricted)
  3. Identify users with import permissions
    Go to Configure > Security > Users, Roles, and Permissions. Review which users or roles have permissions related to file import, project import, or module import capabilities.
    Affected if Any user account with import privileges exists in the system (especially non-administrator accounts with elevated permissions)
  4. Inspect recent file imports
    Review Gateway logs (Status > Logs) or audit logs for recent file import events. Check the projects directory or import history for any recently imported files from external sources.
    Affected if There are recent file import activities, particularly from files sourced outside the organization or from untrusted locations

You are affected if running any Ignition version below 8.3.0 AND the file import feature is enabled with users who have import permissions.

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 8.3.0 or later
Fixed in 8.3.0
Interim mitigation

Restrict file import permissions to only trusted administrators, implement strict file validation and sandboxing for imported files, and monitor/audit file import activities for suspicious behavior.

Recommended fix Moderate confidence

Ignition 8.3.0 or later

  1. 1. Back up your Ignition gateway configuration and any critical project files before upgrading.
  2. 2. Review Ignition 8.3.0 release notes for any migration requirements or注意事项.
  3. 3. Download Ignition version 8.3.0 or later from the official Inductive Automation download page (inductiveautomation.com).
  4. 4. Stop the Ignition gateway service before applying the upgrade.
  5. 5. Install the new version using the official installer, preserving existing configuration when prompted.
  6. 6. Restart the gateway service and verify all modules and projects load correctly.
  7. 7. Review user permissions and consider limiting file import capabilities for non-admin users as a defense-in-depth measure.
Caveat Check 8.3.0 release notes for module compatibility and any configuration changes required; some third-party modules may need updates

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

Fix this in Ignition Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13913 — 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-13913 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