Read the docs

HTML injection in Vikunja notification email header

Priority MEDIUM 56CWE-79Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
Passive
Attack complexity
Low
Attack requirements
None
Impact type
Cross-site scripting
Confidentiality · integrity · availability
None · Low · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-79.

Summary

Vikunja from 2.2.0 before 2.7.1 contains an HTML injection flaw in the notification email header, where display names and task and project titles are inserted into email anchors without escaping (CWE-79). An authenticated user with low privileges can craft a title or display name that closes the anchor and injects phishing links into task comment and mention notification emails sent to project members. User interaction is required.

Written with Claude Haiku 5.5 from the sources below · 2026-11-04

Description from the CNA

Vikunja 2.2.0 before 2.7.1 contains an HTML injection vulnerability in CreateConversationalHeader in pkg/notifications/mail.go that interpolates display names and task and project titles raw into email anchors. Authenticated users can craft titles or display names that close the anchor and inject phishing links into task-comment and task-mention notification emails sent to project members.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00281 20th percentileScored 2026-11-07
Fix Fixed vikunja (go-vikunja): 2.7.1

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
go-vikunjavikunja2.2.0 to before 2.7.12.7.1Patch availableCNA
  • vikunja Vendorgo-vikunja Affected 2.2.0 to before 2.7.1 Fixed in 2.7.1 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:vikunja:vikunja:*:*:*:*:*:*:*:*——go-vikunja
  • cpe:2.3:a:vikunja:vikunja:*:*:*:*:*:*:*:* Versions — — ·go-vikunja

Remediation

Upgrade go-vikunja vikunja to version 2.7.1 or later, which fixes the issue. The sources list no other fixed versions for vikunja.

Written with Claude Haiku 5.5 from the sources below · 2026-11-04

  • Fix · CNA vikunja (go-vikunja) Fixed in 2.7.1

Timeline

  1. 2026-10-22 Threatist record created from CVE-2026-115507
  2. 2026-10-22 Alias added: GHSA-j37p-9r5c-rjgj
  3. 2026-11-04 CISA SSVC decision points changed
  4. 2026-11-04 Priority changed: LOW → MEDIUM

References

  • TI-2026-40929 Authorization bypass in go-vikunja Vikunja CVSS 4.0CRITICAL 9.3
  • TI-2026-21967 Vijkunja has Weak Password Policy Combined with Persistent Sessions After Password Change CVSS 3.1CRITICAL 9.1
  • TI-2026-62115 Vikunja before 2.6.0 Privilege Escalation via Link Share Hash CVSS 4.0HIGH 8.7
  • TI-2026-62108 Vikunja before 2.6.0 Authentication Bypass via CalDAV BasicAuth CVSS 4.0HIGH 8.7
  • TI-2026-62107 Vikunja before 2.6.0 Authentication Bypass via Unthrottled API CVSS 4.0HIGH 8.7
  • TI-2026-26971 Vikunja ahs a TOTP Two-Factor Authentication Bypass via OIDC Login Path CVSS 3.1CRITICAL 9.1
See all 66 →

Sources