dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-65077

HIGH · 8.8 CVSS v4.0 Published 2026-02-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable 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
A relative path traversal vulnerability has been identified in the Embedded Solutions Framework in various Lexmark devices. This vulnerability can be leveraged by an attacker to execute arbitrary code as an unprivileged user.

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 relative path traversal vulnerability in Lexmark devices' Embedded Solutions Framework allows attackers to access files outside intended directories by manipulating path references, potentially leading to arbitrary code execution as an unprivileged user.

MitigationApply the vendor-supplied firmware update for affected Lexmark devices; if unavailable, disable the Embedded Solutions Framework and implement network segmentation to limit exposure.

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
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 Lexmark device model and firmware version
    Access the device web interface or use SNMP/SSH to query the device. For web interface: navigate to Settings > General > About. For command line: telnet or SSH to the device and run 'showsysinfo' or 'version' command. Record the exact model number and firmware version string.
    Affected if The device is a Lexmark printer or MFP and the firmware version is unknown, unpatched, or cannot be verified against vendor advisories.
  2. Verify Embedded Solutions Framework (ESF) status
    Access the device web interface and navigate to Settings > Solutions > Embedded Solutions Framework (or Solutions Framework). Check if the framework is listed as 'Enabled' or 'Running'. Alternatively, from the command line: 'showsystem' or check the solutions status via 'moresys'.
    Affected if Embedded Solutions Framework is enabled or running on the device.
  3. Review ESF solution configuration for custom apps
    In the web interface, go to Settings > Solutions > Solutions. Examine any installed 'Embedded Solutions' or custom applications. Check for unknown or suspicious solution packages (.zxp files). From command line, use 'showextensions' to list loaded solutions.
    Affected if Unknown, untrusted, or recently added solution packages are installed in ESF.
  4. Inspect system logs for path traversal indicators
    Access the device logs via the web interface (Settings > Reports > View Logs) or via command line using 'showlog -p all' or 'nastlog'. Search for entries containing '../', '..\', unusual file read attempts, or access to system directories outside /public/.
    Affected if Logs contain path traversal patterns (../ or ..\) or unexpected file access attempts to sensitive directories.
  5. Check for unauthorized file modifications
    Use the web interface to view the file system (Settings > File Management) or use command line 'ls -l' to compare file timestamps and ownership. Check /mnt/ and /var/ directories for unexpected files. Use 'showsysinfo -f' to review mounted filesystems.
    Affected if New or modified files appear in system directories, or unexpected files exist in locations accessible only through path traversal.

A user is affected if they operate a Lexmark device with Embedded Solutions Framework enabled and either an unverified/unpatched firmware version or evidence of path traversal exploitation in logs or unauthorized file access.

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 the vendor-supplied firmware update for affected Lexmark devices; if unavailable, disable the Embedded Solutions Framework and implement network segmentation to limit exposure.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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