Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Impact | This vulnerability represents critical real-world risk despite the absence of a published CVSS score and EPSS data. The attack vector is network-based (XSS in web frontend), complexity is low (standard DOM-based XSS techniques apply), and no privileges are required—an unauthenticated attacker can often trigger XSS. The technical impact is catastrophic: remote code execution with the privileges of the Electron process user. The vulnerability is not listed in the CISA KEV catalog based on available data, but the presence of a GitHub security advisory (GHSA-xh67-63q3-hf7g) and fixed version (2.2.0) indicates active awareness in the security community. Exploitation is highly automatable—any XSS payload can be weaponized instantly into RCE without additional steps. This is not a high-CVSS-but-low-real-risk issue; it is a genuine priority because it turns a class of web vulnerabilities (XSS) into full system compromise. The fact that a patch has been released suggests the vendor recognized the severity. |
| Exploit ScenarioDerived | An attacker discovers or crafts an XSS vulnerability in the Vikunja web frontend—for example, stored XSS in task descriptions or user comments. When a victim running Vikunja Desktop version 0.21.0 to 2.1.x loads a malicious task, the attacker's JavaScript payload executes in the Electron renderer with nodeIntegration enabled. The payload uses Node.js APIs like require('child_process').exec() to spawn a shell command, stealing sensitive files, installing malware, or establishing a reverse shell on the victim's machine. No user interaction beyond viewing the compromised content is required, and the attack chain is completely automated and reliably exploitable without special privileges. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 24, 2026
The Vikunja Desktop Electron wrapper enables Node.js integration in the renderer process without proper context isolation or sandboxing, allowing any cross-site scripting vulnerability in the web frontend to escalate directly to remote code execution on the victim's machine. Vikunja versions 0.21.0 through 2.1.x are affected, as confirmed by CPE cpe:2.3:a:go-vikunja:vikunja. An attacker exploiting an XSS flaw gains full access to Node.js APIs and the underlying operating system, making this a critical privilege escalation from web-based XSS to system-level RCE.
RemediationAI
Immediately upgrade Vikunja Desktop to version 2.2.0 or later, which disables nodeIntegration and enables contextIsolation and sandbox protections in the Electron renderer. Consult the vendor security advisory at https://github.com/go-vikunja/vikunja/security/advisories/GHSA-xh67-63q3-hf7g for detailed patch notes. For users unable to patch immediately, mitigate by restricting network access to the Vikunja instance to trusted users and networks, enforcing HTTPS with certificate pinning to prevent man-in-the-middle injection of XSS payloads, and disabling or uninstalling the vulnerable Electron desktop application in favor of accessing Vikunja through a web browser with appropriate content security policy controls. Monitor the Vikunja issue tracker for any outstanding XSS vulnerabilities in the web frontend that could be chained with this flaw.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Vikunja is an open-source, self-hosted task management platform built with a web frontend and packaged via Electron for desktop deployment. Electron's nodeIntegration setting, when enabled without contextIsolation or sandbox protections, exposes Node.js APIs directly to renderer processes. This violates the Electron security model, which is designed to isolate untrusted content (web pages) from powerful system APIs. The vulnerability is rooted in CWE-94 (Improper Control of Generation of Code), as injected JavaScript code gains uncontrolled access to Node.js process capabilities. Any XSS flaw in the Vikunja web application—whether present in versions 0.21.0 through 2.1.x or discovered in the future—automatically becomes code injection into a process with system privileges, enabling attackers to read files, execute commands, and compromise the host machine.
Know when Vikunja gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H
Primary rating from GitHub Advisory · only source for this CVE.
CVSS VectorGitHub Advisory
Lifecycle Timeline
2DescriptionGitHub Advisory
Vikunja is an open-source self-hosted task management platform. Starting in version 0.21.0 and prior to version 2.2.0, the Vikunja Desktop Electron wrapper enables nodeIntegration in the renderer process without contextIsolation or sandbox. This means any cross-site scripting (XSS) vulnerability in the Vikunja web frontend -- present or future -- automatically escalates to full remote code execution on the victim's machine, as injected scripts gain access to Node.js APIs. Version 2.2.0 fixes the issue.
Executive ViewAI
Organizations using version 0.21.0 and should be aware of notable risk from CVE-2026-33334, a code injection vulnerability rated CVSS 6.5. Exploitation could allow attackers to execute code or inject malicious input. Organizations should apply vendor updates when available and monitor for exploitation.
Apply vendor patch. If patching is delayed: deploy WAF rules, restrict network access, enable logging.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Cross-tenant information disclosure in the self-hosted task manager Vikunja (0.24.0 through 2.3.0) lets a holder of any
Weak password policy in Vikunja task management before 2.0.0 allows users to set trivially guessable passwords. PoC avai
Principal type confusion in Vikunja (versions 0.22.0-2.3.0) allows an authenticated low-privilege attacker to fully cont
Stored cross-site scripting (XSS) in Vikunja prior to version 2.0.0 allows authenticated attackers to steal authenticati
Vikunja before version 2.0.0 contains a path traversal vulnerability in its backup restoration function that fails to va
Vikunja is an open-source self-hosted task management platform. [CVSS 6.1 MEDIUM]
Business logic vulnerability in Vikunja task management platform before 2.1.0 allows incomplete resource cleanup, potent
Instance-wide data breach in Vikunja before 2.2.1 lets remote attackers exfiltrate and destroy every file attachment acr
Vikunja's OIDC callback handler issues a full JWT to any successfully matched user without checking whether that account
Vikunja instances before 2.6.0 expose CalDAV BasicAuth endpoints (/dav, /.well-known, and /feeds) that are not covered b
Vikunja versions before 2.6.0 ship authentication endpoints under /api/v2 (login, register, password-reset, and OAuth to
Vikunja prior to 2.6.0 leaks the secret hash that backs a project's link shares through its single-share read endpoint,
EUVD-2026-14907
NVD
CVE.org
EPSS
Vulnrichment
GitHub
VulDB
Exploit-DB