Vikunja before 2.7.1 Plugin and Log Directories Not Anchored to Rootpath
- 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.
- Last modified
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.09% · 0th percentile
- 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? →
- 1/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, before version 2.7.1 can load plugins from and write logs to the startup working directory instead of its configured root path. A local attacker with low-privilege access who can write to that directory could plant a malicious plugin that loads when plugins are enabled, or read misplaced logs, including the audit log, and this requires user interaction and an unusual setup.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Vikunja before 2.7.1 fails to re-anchor PluginsDir and LogPath to service.rootpath, allowing plugins to load from and logs to be written in the startup working directory. Local attackers able to write to that directory can plant plugins loaded into the server when plugins are enabled, or read misplaced logs including audit.log.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity1/10CVSS 1.0
- No patch0/5No signal
What would change the score
- Would score about 56 if added to CISA KEV
- Would score about 51 if CISA's SSVC rates exploitation active
- Would score about 23 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
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-123510
Is CVE-2026-123510 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-123510?
vikunja: before 2.7.1.Source: cve.now feed data
How do I fix CVE-2026-123510?
Upgrade to a fixed version: 2.7.1.Source: cve.now feed data