CVE-2026-123510: Vikunja before 2.7.1 Plugin and Log Directories Not Anchored to Rootpath
Noroxi assessment
Priority: Monitor (action score 4/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.09% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. Special conditions such as timing or configuration are required.
- Fixed version: go-vikunja vikunja 2.7.1.
Low priority for now. Upgrade to go-vikunja vikunja 2.7.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Nov 8, 2026
- Updated
- Nov 9, 2026
- EPSS
- 0.0% · 0th percentile
- CWE
- CWE-427
Report tools
Action score
4
Low priority for now.
- CVSS
- 4 / 40 · 1.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.0%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · VulnCheck
- 1.0
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (VulnCheck). Independent of NVD's CPE analysis and usually ahead of it.
go-vikunja vikunja
- 2.7.1not affected
- before 2.7.1affected · semver
Same product
go-vikunja: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-68582Vikunja 0.24.0 Broken Object Level Authorization via Link-Share Token37Monitor
- CVE-2026-123531Vikunja 1.0.0 before 2.7.1 Pagination Limit Bypass via page=0 Parameter34Monitor
- CVE-2026-91985Vikunja before 2.6.0 Privilege Escalation via Link Share Hash34Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-123508Nov 8, 2026 · Vikunja before 2.7.1 Supply Chain Risk via Unpinned xgo Release Toolchain8Monitor
- ← EarlierCVE-2026-123509Nov 8, 2026 · Vikunja before 2.7.1 Denial of Service via Unbounded Kanban Bucket Count21Monitor
- Later →CVE-2026-123511Nov 8, 2026 · Vikunja before 2.7.1 Resource Exhaustion via CalDAV VTODO RELATED-TO Entries21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| go-vikunja vikunja | 2.7.1 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 13, 2026+6 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- P
- Scope
- X
Weakness class (CWE)
CWE-427 · Uncontrolled Search Path ElementCVSS vector
CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
- Hijack Execution Flow:DLL search order hijackingT1574.001
- Hijack Execution Flow: Dylib HijackingT1574.004
- Hijack Execution Flow: Path Interception by PATH Environment VariableT1574.007
- Hijack Execution Flow: Path Interception by Search Order HijackingT1574.008
- Hijack Execution Flow: Path Interception by Unquoted PathT1574.009
Change log
- SSVC exploitation— → none
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.