CVE-2026-27616: Vikunja Cross-Site Scripting Vulnerability
HIGHCVE-2026-27616 is a HIGH (CVSS 7.3) cross-site scripting vulnerability (CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')) affecting Vikunja libraries in the Go ecosystem. The issue involves stored xss via unsanitized svg attachment upload leads to token exposure. Remediation is available in the latest vendor maintenance releases.
CVE-2026-27616 at a Glance
Security Impact
CVSS: 7.3
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N).
How to Fix CVE-2026-27616
To remediate this vulnerability, upgrade all affected Vikunja dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade code.vikunja.io/api to Latest secure release
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for code.vikunja.io/api
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-27616, inspect your project dependencies for Vikunja:
inspect dependencies for code.vikunja.io/api
Analyze the terminal output to locate any version of Vikunja in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'), where the product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. In Vikunja, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-27616 Affected Vikunja Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
code.vikunja.io/api
|
Go |
≤ 0.24.6
|
|
References
Frequently Asked Questions
What is CVE-2026-27616?
Which Vikunja versions are affected?
What version fixes CVE-2026-27616?
Is code.vikunja.io/api affected?
What is the CVSS score of CVE-2026-27616?
What CWE is associated with CVE-2026-27616?
How can I check Go dependencies for CVE-2026-27616?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-7jp5-298q-jg98",
"modified" : "2026-02-27T21:52:14Z",
"published" : "2026-02-25T22:40:15Z",
"aliases" : [ "CVE-2026-27616" ],
"summary" : "Vikunja: Stored XSS via Unsanitized SVG Attachment Upload Leads to Token Exposure",
"details" : "**Details**\nThe application allows users to upload SVG files as task attachments. SVG is an XML-based format that supports JavaScript execution through elements such as <script> tags or event handlers like onload.\n\nThe application does not sanitize SVG content before storing it. When the uploaded SVG file is accessed via its direct URL, it is rendered inline in the browser under the application's origin. As a result, embedded JavaScript executes in the context of the authenticated user.\n\nBecause the authentication token is stored in localStorage, it is accessible via JavaScript and can be retrieved by a malicious payload.\n\nKey security issues identified:\n\n _No server-side sanitization of SVG content.\nSVG attachments are rendered inline instead of being forced as a download.\nEmbedded JavaScript within SVG files is allowed to execute.\n Authentication tokens stored in localStorage are accessible to client-side scripts._\n\n**PoC**\n\n_**Tested Environment**_\n\n[ ] Application version: 1.1.0\n[ ] Deployment type: Self-hosted\n\n**Steps to Reproduce**\n\n1. Log in to an account.\n2. Go to Projects and Create a new task or open an existing task.\n3. Upload the following SVG file as an attachment:\n\n```\n<?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"yes\"?>\n<svg\n onload=\"alert(localStorage.getItem('token'))\"\n xmlns=\"http://www.w3.org/2000/svg\">\n</svg>\n\n```\n4. After uploading ,save the Task and open the project , copy the direct URL of the attachment.\n5. Open the attachment URL in a new browser tab.\n6. The embedded JavaScript executes immediately and displays the authentication token stored in `localStorage`.\n\nThis confirms that arbitrary JavaScript embedded in an uploaded SVG file executes within the application's context.\n\n**Impact**\n\nThis vulnerability is classified as **Stored Cross-Site Scripting (XSS).**\n\n**Potential impact includes:**\n\nExecution of arbitrary JavaScript in a victim’s browser.\nExposure of authentication tokens.\nPotential account takeover.\nAbility to perform authenticated actions on behalf of the victim.\nPossible privilege escalation if higher-privileged users open the malicious attachment.\nAny authenticated user who accesses a malicious SVG attachment may be affected.\n\n**Recommendations**\n\nThis vulnerability can be mitigated by implementing proper server-side sanitization of SVG uploads and preventing inline execution of uploaded files.\n\nSpecifically:\n\n- Sanitize all uploaded SVG files to remove <script> elements, event handlers (e.g., onload), and other executable content.\n- Serve attachments with Content-Disposition: attachment to prevent inline rendering.\n- Implement a strict Content Security Policy (CSP) to block script execution within uploaded files.\n- Store authentication tokens in HttpOnly, Secure cookies instead of localStorage to prevent JavaScript access.\n- Applying these controls will prevent stored XSS via SVG uploads and significantly reduce the risk of token exposure and account takeover.\n\n**Attachment**\n[Stored XSS Proof of concept.pdf](https://github.com/user-attachments/files/25414870/Stored.XSS.Proof.of.concept.pdf)\n\nA fix is available at https://github.com/go-vikunja/vikunja/releases/tag/v2.0.0.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "code.vikunja.io/api"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"last_affected" : "0.24.6"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/go-vikunja/vikunja/security/advisories/GHSA-7jp5-298q-jg98"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-27616"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/go-vikunja/vikunja"
}, {
"type" : "WEB",
"url" : "https://github.com/go-vikunja/vikunja/releases/tag/v2.0.0"
}, {
"type" : "WEB",
"url" : "https://github.com/user-attachments/files/25414870/Stored.XSS.Proof.of.concept.pdf"
}, {
"type" : "WEB",
"url" : "https://vikunja.io/changelog/vikunja-v2.0.0-was-released"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-79" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-02-25T22:40:15Z",
"nvd_published_at" : "2026-02-25T22:16:26Z"
}
}