LiveActive security incident?Get immediate response
CVE Record

CVE-2026-27616: Vikunja Vulnerable to Stored Cross-Site Scripting (XSS) via Unsanitized SVG Attachment Upload Leading to Token Exposure

Vikunja is an open-source self-hosted task management platform. Prior to version 2.0.0, the 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. The 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. Because the authentication token is stored in localStorage, it is accessible via JavaScript and can be retrieved by a malicious payload. Version 2.0.0 patches this issue.

HighCVSS 7.3Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-27616 affects Vikunja, a self-hosted task management platform, before version 2.0.0. A malicious authenticated user can upload an SVG attachment that runs JavaScript when another user opens it. Because Vikunja stores the authentication token in localStorage, the script may expose that token, risking account takeover and unauthorized access to tasks or projects.

Executive priority

Treat this as a high-priority update for any Vikunja instance handling sensitive work, customer data, or privileged internal tasks. The fix is available in version 2.0.0. Prioritize internet-facing or multi-user deployments first, especially where untrusted users can upload attachments.

Technical view

The issue is stored cross-site scripting in SVG task attachments. Vikunja versions before 2.0.0 store SVG content without sanitizing embedded script-capable elements. When the SVG is accessed directly, the browser renders it under the Vikunja origin, allowing JavaScript execution as the viewing authenticated user. The advisory maps this to CWE-79 with CVSS 7.3 high severity.

Likely exposure

Exposure is limited to Vikunja deployments running versions earlier than 2.0.0 where users can upload task attachments and other authenticated users may access those attachments. Self-hosted instances are the primary concern. Public internet exposure increases business risk, but exploitation still requires a logged-in user to upload and another user to interact.

Exploitation context

The provided sources describe a proof of concept and a patch, but do not state active exploitation in the wild. The attack requires low privileges and user interaction. The main impact is confidentiality and integrity loss through JavaScript execution in the application origin and possible theft of authentication tokens stored in localStorage.

Researcher notes

Evidence comes from the CVE record, GitHub advisory, a referenced proof-of-concept PDF, and Vikunja 2.0.0 release notes. Do not assume broader product impact beyond go-vikunja/vikunja before 2.0.0. No KEV listing or cited source confirms active exploitation.

Mitigation direction

  • Upgrade Vikunja to version 2.0.0 or later.
  • Review the GitHub security advisory for vendor-confirmed remediation details.
  • Restrict attachment uploads if immediate upgrade is not possible.
  • Consider removing or quarantining untrusted SVG attachments.
  • Monitor for suspicious account activity after exposure.

Validation and detection

  • Inventory all Vikunja instances and confirm running versions.
  • Check whether any instance is below version 2.0.0.
  • Review task attachments for uploaded SVG files.
  • Confirm upgraded instances no longer render unsafe SVG content inline.
  • Review logs for unusual attachment access or account activity.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-27616 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.3CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N2.15.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.3High
CVSS 3.1 vector shape for CVE-2026-27616Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
go-vikunjavikunja< 2.0.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.