dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-25069

CRITICAL · 9.3 CVSS v4.0 Published 2026-02-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/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
SunFounder Pironman Dashboard (pm_dashboard) version 1.3.13 and prior contain a path traversal vulnerability in the log file API endpoints. An unauthenticated remote attacker can supply traversal sequences via the filename parameter to read and delete arbitrary files. Successful exploitation can disclose sensitive information and delete critical system files, resulting in data loss and potential system compromise or denial of service.

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

The SunFounder Pironman Dashboard (pm_dashboard) versions 1.3.13 and prior contains a path traversal vulnerability in its log file API endpoints. An unauthenticated remote attacker can exploit this by supplying path traversal sequences (such as ../) through the filename parameter to access files outside the intended directory. This allows arbitrary file read and delete operations, enabling disclosure of sensitive information, deletion of critical system files, and potential denial of service.

MitigationImplement strict input validation and sanitization on the filename parameter to reject path traversal sequences, apply allow-listing of permitted file paths, and enforce proper authentication/authorization on all log file API endpoints.

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:H/VI:H/VA:H/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. Confirm pm_dashboard installation
    Locate and identify the SunFounder Pironman Dashboard pm_dashboard application in your environment. Check running services, installed packages, or application directories where this dashboard may be installed.
    Affected if The pm_dashboard software is present and running in your environment.
  2. Determine pm_dashboard version
    Identify the installed version of pm_dashboard by checking application metadata, package version, or the dashboard's 'About' or version information page. Compare the found version against the affected range: versions 1.3.13 and prior.
    Affected if The installed version is 1.3.13 or any earlier version.
  3. Verify log file API endpoint accessibility
    Locate the log file API endpoints provided by pm_dashboard. These are the endpoints that handle log file operations. Determine if these endpoints respond to requests without requiring authentication.
    Affected if The log file API endpoints are accessible without any authentication.
  4. Check for input validation on filename parameter
    Test or inspect the log file API endpoints to see if they accept a 'filename' parameter. Attempt to verify whether the application rejects path traversal sequences like '../' in the filename parameter, or examine the API code/configuration for input validation logic.
    Affected if The API accepts a filename parameter and does not block '../' traversal sequences, allowing access outside the intended log directory.

Your environment is affected if pm_dashboard version 1.3.13 or prior is installed, the log file API endpoints are accessible without authentication, and the application does not reject traversal sequences in the filename parameter.

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

Implement strict input validation and sanitization on the filename parameter to reject path traversal sequences, apply allow-listing of permitted file paths, and enforce proper authentication/authorization on all log file API endpoints.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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