cve.bz

CVE-2026-123515

5.1 mediumEPSS 0.2%

Medium (5.1) in go-vikunja vikunja. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
Vikunja before 2.7.1 contains a client-side request forgery vulnerability that allows users with write access to make viewers' clients request loopback or LAN addresses by storing img elements in rich text. Attackers can plant images in tasks, comments, project descriptions, or imported Markdown to trigger blind GET requests against local services and track when viewers open content.

Severity

CVSS 4.0

5.1 medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N

CVSS 3.1

4.1 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:L/A:N
EPSS
0.2% estimated probability of exploitation activity in the next 30 days; 6th percentile. Scored 2026-11-10. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-441 Unintended Proxy or Intermediary (Confused Deputy)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-123515 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-123515?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-123515?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-123515 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
go-vikunja vikunjabefore 2.7.1

Attack patterns (CAPEC)

  • CAPEC-219 XML Routing Detour Attacks Likelihood: High · Severity: Medium
  • CAPEC-465 Transparent Proxy Abuse Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON