dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-3465

HIGH · 7.1 CVSS v3.1 Published 2025-10-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
76/100
Remediation priority · High
No privileges 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
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in ABB CoreSense™ HM, ABB CoreSense™ M10.This issue affects CoreSense™ HM: through 2.3.1; CoreSense™ M10: through 1.4.1.12.

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

A path traversal vulnerability in ABB CoreSense HM (through 2.3.1) and CoreSense M10 (through 1.4.1.12) allows attackers to access files and directories outside the intended restricted directory through specially crafted pathname inputs in the application.

MitigationApply vendor-provided security patches or firmware updates to address the path traversal vulnerability. If patches are unavailable, implement strict input validation and path sanitization to ensure all file path references remain within allowed directories.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

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

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 ABB CoreSense product
    Locate and inspect the CoreSense HM or CoreSense M10 installation. Check system inventory, software listings, or device management interfaces for these product names.
    Affected if The product is ABB CoreSense HM or CoreSense M10
  2. Determine installed version of CoreSense HM
    Access the system administration interface, check firmware version through the device console, or review system documentation and release notes. Look for version information in the about or system info section.
    Affected if Version is 2.3.1 or lower (any version through 2.3.1)
  3. Determine installed version of CoreSense M10
    Access the system administration interface, check firmware version through the device console, or review system documentation and release notes. Look for version information in the about or system info section.
    Affected if Version is 1.4.1.12 or lower (any version through 1.4.1.12)
  4. Verify web application interface is accessible
    Check if the CoreSense web interface or API endpoint is reachable from the network. Attempt to access the application login or status page.
    Affected if The application web interface is exposed and accessible

The environment is affected if CoreSense HM version 2.3.1 or lower, or CoreSense M10 version 1.4.1.12 or lower, is installed and the application interface is 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-provided security patches or firmware updates to address the path traversal vulnerability. If patches are unavailable, implement strict input validation and path sanitization to ensure all file path references remain within allowed directories.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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