CVE-2025-8343VulnerabilityPublished 31 Jul 2025

CVE-2025-8343: openviglet shio · Path Traversal

Affects openviglet shioSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.9% chance of exploitation in 30 days – higher than 60% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 31 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
openviglet shio	Affected =0.3.0 =0.3.1 =0.3.2 =0.3.3 =0.3.4 =0.3.5 =0.3.6 =0.3.7 =0.3.8	Fixed in–

AI-suggested

To mitigate CVE-2025-8343, European organizations should take the following specific actions: 1) Immediately audit all deployments of openviglet shio to identify affected versions (0.3.0 to 0.3.8). 2) Restrict access to the shStaticFilePreUpload API endpoint to trusted and authenticated users only, enforcing strong authentication and authorization controls. 3) Implement input validation and sanitization at the application or web server level to block path traversal characters such as '../' sequences in fileName parameters. 4) Employ web application firewalls (WAFs) with custom rules to detect and block path traversal attack patterns targeting the vulnerable endpoint. 5) Isolate the application environment with strict filesystem permissions, ensuring the application process has access only to necessary directories, limiting the impact of any traversal attempts. 6) Monitor logs for suspicious file access patterns or failed attempts to access unauthorized paths. 7) Engage with the openviglet project or vendor for patches or updates addressing this vulnerability and plan prompt deployment once available. 8) Consider temporary disabling or restricting the static file upload feature if feasible until a patch is applied.

Description

A vulnerability was found in openviglet shio up to 0.3.8. It has been rated as critical. This issue affects the function shStaticFilePreUpload of the file shio-app/src/main/java/com/viglet/shio/api/staticfile/ShStaticFileAPI.java. The manipulation of the argument fileName leads to path traversal. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.

Impact

For European organizations using openviglet shio versions 0.3.0 to 0.3.8, this vulnerability presents a risk of unauthorized access to sensitive files on servers hosting the application. Given that the vulnerability allows remote exploitation without user interaction, attackers could leverage it to read configuration files, credentials, or other sensitive data stored on the server, potentially leading to further compromise. Organizations in sectors with strict data protection regulations, such as finance, healthcare, and government, could face compliance violations if sensitive personal or business data is exposed. The impact is somewhat mitigated by the requirement of low-level privileges (PR:L), meaning an attacker must have some level of authenticated access, but this is still a significant risk if the application is exposed to untrusted users or if authentication controls are weak. The medium CVSS score reflects a moderate risk, but the critical rating mentioned in the description suggests that in certain deployment contexts, the impact could be more severe. European entities relying on openviglet shio for web content management or static file handling should assess their exposure, especially if the application is internet-facing or integrated with sensitive backend systems.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 31 Jul 2025, 01:32 UTC

Technical details

References

Community reviews

Related threats