dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-2864

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 vulnerability has been found in feng_ha_ha/megagao ssm-erp and production_ssm up to 4288d53bd35757b27f2d070057aefb2c07bdd097. This affects the function pictureDelete of the file PictureController.java. Such manipulation of the argument picName leads to path traversal. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. 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

Path traversal vulnerability in the pictureDelete function of PictureController.java in the megagao ssm-erp/production_ssm project. The picName argument is not properly validated, allowing attackers to manipulate path sequences (e.g., ../../) to delete files outside the intended directory. The exploit is publicly available and can be launched remotely.

MitigationImplement strict input validation on the picName parameter to reject path traversal sequences and restrict file operations to an allowed directory whitelist. Consider using canonical path resolution to verify the final path is within the intended directory before deletion.

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. Identify if megagao ssm-erp is deployed
    Search the codebase or deployed application for the 'ssm-erp' or 'production_ssm' project structure, specifically looking for PictureController.java in the controller layer
    Affected if The application contains the megagao ssm-erp/production_ssm project with PictureController.java
  2. Locate pictureDelete function in PictureController.java
    Find PictureController.java in the source code or decompiled application and locate the pictureDelete method that accepts a picName parameter
    Affected if The pictureDelete function exists and processes a picName parameter without proper validation
  3. Verify picName parameter validation is absent
    Examine the pictureDelete function code to check if input validation exists for the picName argument - specifically look for path traversal pattern checks (../, ..\) or whitelist validation
    Affected if The picName parameter is used directly in file operations without sanitization or validation logic
  4. Confirm network accessibility of the delete endpoint
    Determine if the pictureDelete endpoint is exposed via HTTP/HTTPS and accessible from remote locations by reviewing web.xml, controller mappings, or network configuration
    Affected if The endpoint is reachable remotely without authentication or IP restrictions
  5. Check for path traversal attempts in access logs
    Review web server or application access logs for unusual requests containing ../ patterns targeting the pictureDelete endpoint
    Affected if Exploitation attempts with ../ sequences are visible in logs

You are affected if the megagao ssm-erp/production_ssm application is deployed with PictureController.java containing a pictureDelete function that processes the picName parameter without validating or sanitizing path traversal sequences, and the endpoint is network-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

Implement strict input validation on the picName parameter to reject path traversal sequences and restrict file operations to an allowed directory whitelist. Consider using canonical path resolution to verify the final path is within the intended directory before deletion.

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-2864 — 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-2864 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