Vikunja 0.22.0 before 2.7.1 Webhook URL Credential Exposure to Read-Only Members
- Exploited
- No known exploitation
- Fix
- Fixed in 2.7.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2.7.1.
- Published
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 8/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Vikunja, a task-management application, is affected by a flaw that lets any read-only project member see the full webhook target URLs by listing a project's webhooks. The attacker can do this remotely with a low-privilege login and no user action, and can use the exposed tokens or API keys embedded in those URLs to post to receiving channels or reuse the keys until they are rotated.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Vikunja from 0.22.0 before 2.7.1 contains an information disclosure vulnerability that allows read-only project members to view full webhook target URLs by listing project webhooks. Attackers can extract incoming-webhook tokens or API keys embedded in target_url values to post to receiving channels or reuse keys until rotated.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 2.7.1.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- go-vikunja vikunja
From 0.22.0 · fixed in 2.7.1
Evidence 2
- Advisory
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123504
Is CVE-2026-123504 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-123504?
vikunja: from 0.22.0 before 2.7.1.Source: cve.now feed data
How do I fix CVE-2026-123504?
Upgrade to a fixed version: 2.7.1.Source: cve.now feed data