Sploit.io - Search

Product: D-Guard, version: 20250206

CVE-2025-1357

Severity: Unknown

Description: A vulnerability classified as problematic has been found in Seventh D-Guard up to 20250206. This affects an unknown part of the component HTTP GET Request Handler. The manipulation leads to path traversal. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

CVSS Score: N/A

Priority

D

CISA Data

EPSS Data

  • EPSS: 0.001340000
  • Percentile: 0.328200000
  • Date: 2026-03-14

ExploitDB

No data available.

HackerOne Data

  • Rank: 8904
  • Reports submitted count: 0
  • Unknown: 0
  • None: 0
  • Low: 0
  • Medium: 0
  • High: 0
  • Critical: 0

GitHub PoCs

    Nuclei Templates

    No data available.

    VulnCheck Data

    Affected Products:

    • Seventh D-Guard - Versions: 20250206

    References:

    Risk Assessment

    1. Risk Assessment
    The vulnerability identified in Seventh D-Guard, CVE-2025-1357, is a path traversal vulnerability affecting the HTTP GET Request Handler. This allows a remote attacker with limited privileges to potentially access files and directories on the system beyond the intended webroot. The vulnerability is classified as problematic with a CVSS score of 4.3 (Medium), indicating a moderate risk. The likelihood of exploitation is reasonably high as the exploit is publicly disclosed and the vendor has been slow to respond. The vulnerability primarily impacts confidentiality, as an attacker can potentially read sensitive files. Integrity and availability are less directly impacted, but could be affected if the attacker gains access to configuration files or can exhaust server resources during file access. The EPSS score of 0.001340000 suggests a relatively low, but not negligible, probability of exploitation in the wild.

    2. Potential Attack Scenarios
    An attacker could leverage the path traversal vulnerability to access sensitive configuration files. The attack vector involves crafting a malicious HTTP GET request with a specially crafted path. The attacker sends a GET request to Seventh D-Guard, including a path that utilizes "..\" sequences to navigate up the directory structure, eventually reaching sensitive files like database connection strings or application configuration files. The attack process begins with reconnaissance to understand the directory structure, followed by crafting the malicious request, and finally, analyzing the response to confirm access to the target file. A successful attack outcome could reveal database credentials, leading to potential data exfiltration or further compromise of the system.

    3. Mitigation Recommendations
    The primary mitigation for CVE-2025-1357 is to upgrade Seventh D-Guard to a version beyond 20250206, once a patched version is released. In the interim, implement input validation on the HTTP GET request parameters to sanitize the path and prevent traversal sequences like "..\" from being interpreted as directory navigators. Consider using a Web Application Firewall (WAF) to filter malicious requests and detect path traversal attempts. Regularly monitor logs for unusual file access patterns that could indicate exploitation. While there isn't a dedicated Nuclei template currently, monitoring PacketStorm Security (https://packetstormsecurity.com/search/?q=CVE-2025-1357) for updated exploits and VulDB (https://vuldb.com/?id.295965) for further information is recommended.

    4. Executive Summary
    Seventh D-Guard is affected by a path traversal vulnerability (CVE-2025-1357) that could allow attackers to remotely access sensitive files on the system. This is a medium-risk vulnerability, as the exploit is publicly available and the vendor has been slow to respond. A successful attack could lead to the compromise of configuration files and potentially database credentials, impacting data confidentiality. We recommend upgrading to the latest version of Seventh D-Guard as soon as a patch is available. In the meantime, implementing input validation and using a Web Application Firewall can help mitigate the risk. Addressing this vulnerability is important to protect sensitive data and maintain the integrity of our systems. The vendor’s lack of response to the initial disclosure increases the urgency of addressing this issue proactively.