Summary
Workarounds
Restrict access to the cloudstore.file.upload action through authentication and authorization controls until a patch is available.
Impact
The cloudstore.file.upload action in server/actions/action_cloudstore_file_upload.go writes user-supplied filenames directly to disk without proper validation.
This allows unauthenticated attackers to perform path traversal and zip slip attacks, leading to arbitrary file write and potential remote code execution.
CVSS Score: 10.0 Critical
CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H
CWE: CWE-22 (Path Traversal)
Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.
GHSA-9CP7-J3F8-P5JX has a CVSS score of 10.0 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.12.0); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Upgrade to a patched version once released. The vulnerability affects all versions <= v0.11.3 (latest).
Frequently Asked Questions
- What is GHSA-9CP7-J3F8-P5JX? GHSA-9CP7-J3F8-P5JX is a critical-severity path traversal vulnerability in github.com/daptin/daptin (go), affecting versions <= 0.11.3. It is fixed in 0.12.0. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
- How severe is GHSA-9CP7-J3F8-P5JX? GHSA-9CP7-J3F8-P5JX has a CVSS score of 10.0 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of github.com/daptin/daptin are affected by GHSA-9CP7-J3F8-P5JX? github.com/daptin/daptin (go) versions <= 0.11.3 is affected.
- Is there a fix for GHSA-9CP7-J3F8-P5JX? Yes. GHSA-9CP7-J3F8-P5JX is fixed in 0.12.0. Upgrade to this version or later.
- Is GHSA-9CP7-J3F8-P5JX exploitable, and should I be worried? Whether GHSA-9CP7-J3F8-P5JX is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-9CP7-J3F8-P5JX is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-9CP7-J3F8-P5JX? Upgrade
github.com/daptin/daptinto 0.12.0 or later.