dbcve.org
ShioApplication · Viglet

CVE-2025-8344

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-31
Fix available
A fix is available. Upgrade to after 0.3.8 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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 vulnerability classified as critical has been found in openviglet shio up to 0.3.8. Affected is the function shStaticFileUpload of the file shio-app/src/main/java/com/viglet/shio/api/staticfile/ShStaticFileAPI.java. The manipulation of the argument filename leads to unrestricted upload. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.

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 ShStaticFileAPI in openviglet shio up to 0.3.8 contains an unrestricted file upload vulnerability in the shStaticFileUpload function. The filename argument is not validated, allowing remote attackers to upload arbitrary files (including executable web shells) to the server without proper sanitization or restrictions.

MitigationImplement strict validation of the filename parameter, enforce allowed file type whitelist, store uploads outside the web root, and verify file content matches the declared type before saving.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ShioApplication
Affected:<= 0.3.8

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

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

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 Viglet Shio installation and version
    Locate the Shio application and determine its installed version. Check the application's version file, about page, or startup logs for the version number. Common locations include the application root directory, configuration files, or the web interface.
    Affected if The installed version is Viglet Shio version 0.3.8 or lower.
  2. Confirm ShStaticFileAPI is exposed
    Identify if the ShStaticFileAPI endpoint is accessible in the deployment. This is typically exposed as a REST endpoint (often at a path containing 'staticfile' or 'upload'). Check the application's API documentation or route configuration to locate this endpoint.
    Affected if The ShStaticFileAPI endpoint is reachable and accepts HTTP requests.
  3. Verify shStaticFileUpload function is enabled
    Check if the file upload functionality within ShStaticFileAPI is enabled and accessible. This may be a specific upload endpoint or method within the API. Review the API configuration or try to access the upload function directly.
    Affected if The shStaticFileUpload function is enabled and accepts file upload requests without authentication or authorization checks.
  4. Inspect file upload access controls
    Examine the access control configuration for the upload endpoint. Determine if anonymous or unauthenticated users can invoke the upload function. Check for any API keys, tokens, or session requirements.
    Affected if The upload endpoint allows requests without proper authentication or allows arbitrary file types to be uploaded.

You are affected if Viglet Shio version 0.3.8 or lower is running with the ShStaticFileAPI and its upload function exposed and accessible without strict validation on 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
Upgrade available Upgrade to a release after 0.3.8
Interim mitigation

Implement strict validation of the filename parameter, enforce allowed file type whitelist, store uploads outside the web root, and verify file content matches the declared type before saving.

Fix this in Shio Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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