VulnerabilityPublished 27 Jun 2025

CVE-2025-6774: gooaclok819 sublinkX · Path Traversal

Affects gooaclok819 sublinkXSource CVE Database V5

Public exploit available · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score

5.3Medium

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 36% 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:L/VA:L/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: Low
Vulnerable system availability: Low
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: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to 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 27 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

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 or the CVSS exploit maturity 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
GitHubgooaclok819/sublinkX`pkg:github/gooaclok819/sublinkX`Other threats	Affected 1.0 – 1.8 9 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Immediate upgrade to sublinkX version 1.9 or later, which contains the official patch addressing the path traversal vulnerability.
If immediate upgrade is not feasible, implement input validation and sanitization on the filename parameter at the application or web server level to block directory traversal characters such as '../'.
Employ web application firewalls (WAFs) with custom rules to detect and block path traversal attack patterns targeting the AddTemp function or related API endpoints.
Restrict file system permissions for the sublinkX application user to the minimum necessary, preventing access to sensitive directories and files outside the application scope.
Monitor logs for suspicious requests containing directory traversal sequences or unusual file access patterns.
Conduct a thorough audit of exposed files and credentials on affected systems to identify any potential data leakage.
Educate development and operations teams about secure coding practices to prevent similar vulnerabilities in future releases.

Description

A vulnerability was found in gooaclok819 sublinkX up to 1.8. It has been rated as critical. Affected by this issue is the function AddTemp of the file api/template.go. The manipulation of the argument filename leads to path traversal. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 1.9 is able to address this issue. The patch is identified as 778d26aef723daa58df98c8060c43f5bf5d1b10b. It is recommended to upgrade the affected component.

Impact

For European organizations, this vulnerability poses a risk primarily to confidentiality, as attackers could access sensitive configuration files, credentials, or other protected data stored on servers running vulnerable versions of sublinkX. This could lead to further compromise if sensitive information such as database credentials or private keys is exposed. The integrity and availability impacts are limited since the vulnerability does not allow direct modification or deletion of files or remote code execution. However, the exposure of sensitive data could facilitate subsequent attacks, including privilege escalation or lateral movement within networks. Organizations in sectors with strict data protection regulations, such as finance, healthcare, and government, could face compliance and reputational risks if data is leaked. The remote and unauthenticated nature of the exploit increases the urgency of patching, especially for externally facing systems. Since no known exploits are currently active in the wild, organizations have a window to remediate before widespread attacks occur.

Summary

CVE-2025-6774 is a path traversal vulnerability identified in the gooaclok819 sublinkX software, affecting all versions up to 1.8. The vulnerability resides specifically in the AddTemp function within the api/template.go source file. The flaw arises from improper validation or sanitization of the filename argument, which allows an attacker to manipulate the input to traverse directories outside the intended file path. This can enable unauthorized access to arbitrary files on the server hosting sublinkX. The vulnerability can be exploited remotely without requiring user interaction or authentication, increasing its risk profile. Although the CVSS 4.0 base score is 5.3 (medium severity), the vulnerability's ability to expose sensitive files or system data can have significant consequences depending on the deployment context. The vendor has addressed the issue in version 1.9, and a patch identified by commit 778d26aef723daa58df98c8060c43f5bf5d1b10b is available. No known exploits are currently reported in the wild, but public disclosure of the exploit code means attackers could develop weaponized attacks quickly. The vulnerability does not require privileges or user interaction, and the attack vector is network-based, making it accessible to remote adversaries. The impact on confidentiality, integrity, and availability is low to moderate, as the attacker can read arbitrary files but cannot directly modify or delete files or execute code through this flaw alone.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Jun 2025, 19:54 UTC

Technical details

References

Community reviews

Related threats