Summary
Vikunja: Cross-project task disclosure through subtask expansion
Impact
Cross-project confidentiality break. A user with read access to one project can read the full content of tasks in other projects they were never granted access to, whenever those tasks are linked as subtasks (directly or recursively) under a task they can see. The disclosure is read-only, no modification, but it exposes arbitrary private task data, and it survives access revocation, since the underlying links remain after a collaborator is removed. Exploitation depends on a suitable cross-project subtask link already existing; the attacker cannot create one to a project they can't access.
The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.
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.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-3HC7-R24J-RPWC? GHSA-3HC7-R24J-RPWC is a medium-severity missing authorization vulnerability in code.vikunja.io/api (go), affecting versions <= 2.5.0. It is fixed in 2.6.0. The application does not perform an authorization check before performing a sensitive operation.
- Which versions of code.vikunja.io/api are affected by GHSA-3HC7-R24J-RPWC? code.vikunja.io/api (go) versions <= 2.5.0 is affected.
- Is there a fix for GHSA-3HC7-R24J-RPWC? Yes. GHSA-3HC7-R24J-RPWC is fixed in 2.6.0. Upgrade to this version or later.
- Is GHSA-3HC7-R24J-RPWC exploitable, and should I be worried? Whether GHSA-3HC7-R24J-RPWC 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-3HC7-R24J-RPWC 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-3HC7-R24J-RPWC? Upgrade
code.vikunja.io/apito 2.6.0 or later.