dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-2863

MEDIUM · 5.4 CVSS v3.1 Published 2026-02-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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 flaw has been found in feng_ha_ha/megagao ssm-erp and production_ssm up to 4288d53bd35757b27f2d070057aefb2c07bdd097. The impacted element is the function deleteFile of the file FileServiceImpl.java. This manipulation causes path traversal. The attack can be initiated remotely. The exploit has been published and may be used. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available. This product is distributed under two entirely different names. The project was informed of the problem early through an issue report but has not responded yet.

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 exists in the deleteFile function of FileServiceImpl.java in the megagao ssm-erp system. The vulnerability allows attackers to manipulate file paths in delete operations to access or delete files outside the intended directory through directory traversal sequences (e.g., '../').

MitigationImplement strict input validation on file path parameters using canonical path resolution (realPath) to ensure the resolved path remains within allowed directories. Additionally, apply allowlist-based filtering for permitted delete paths and consider removing the affected endpoint if not business-critical.

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

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

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 megagao ssm-erp deployment
    Search the deployment artifacts (WAR files, JAR files, or source code) for references to 'ssm-erp' or 'megagao' in application metadata, pom.xml, or configuration files.
    Affected if The application is identified as megagao ssm-erp or a derivative.
  2. Locate FileServiceImpl.java
    Search the codebase for the file FileServiceImpl.java, typically found under src/main/java with a package path containing 'file' or 'service'.
    Affected if FileServiceImpl.java exists in the application codebase.
  3. Verify deleteFile method exists
    Open FileServiceImpl.java and locate the deleteFile method - look for a method accepting a file path parameter and performing file deletion operations.
    Affected if A deleteFile method with file path handling is present in FileServiceImpl.java.
  4. Check deleteFile endpoint exposure
    Search for controller classes (typically annotated with @RestController or @Controller) that reference FileServiceImpl or the deleteFile method. Look for request mappings like @RequestMapping, @PostMapping, or @GetMapping with paths containing 'file', 'delete', or similar.
    Affected if An HTTP endpoint maps to the deleteFile functionality and is accessible.
  5. Inspect input validation on file path parameter
    Review the deleteFile method and its calling controller for input validation logic. Look for use of realPath(), canonicalPath(), or allowlist filtering on the file path parameter. Check if '../' sequences are filtered or blocked.
    Affected if No canonical path validation (realPath/canonicalPath) or allowlist filtering is implemented on the file path parameter before deletion.

Your environment is affected if you are running the megagao ssm-erp system with the deleteFile function exposed and without proper canonical path validation on file path parameters used in deletion operations.

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 on file path parameters using canonical path resolution (realPath) to ensure the resolved path remains within allowed directories. Additionally, apply allowlist-based filtering for permitted delete paths and consider removing the affected endpoint if not business-critical.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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