Skip to main content

Otter Wiki CVE-2026-120501

| EUVDEUVD-2026-115253 MEDIUM
Files or Directories Accessible to External Parties (CWE-552)
2026-11-02 VulnCheck GHSA-vqc6-v48c-q9rf
6.9
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Access wiki as anonymous editor
  2. Exploit
    Inject DataTable embedding with src=/.git/config
  3. Execution
    Server renders internal file as table
  4. Impact
    Disclose git remote credentials

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling File access restriction
MITRE ATT&CK

2 techniques across 1 tactic: Collection

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

The attacker must be able to edit a wiki page; under Otter Wiki's default configuration this includes anonymous (unauthenticated) users, which is why no account is required by default. The specific prerequisite is the DataTable embedding feature accepting an absolute src value (e.g. {{datatable |src=/.git/config}}), which the server resolves and renders as a table, including files inside the repository's .git directory. The vendor fix also addresses two related conditions shown in the tests: case-insensitive filesystems where .GIT equals .git, and symlinks (e.g. pushed via git) pointing into .git. Exploitation is LIMITED on instances that disable anonymous editing or restrict page-edit rights, where an attacker would need a valid account with edit permissions; impact is bounded to reading repository-internal files (notably git remote credentials) and does not include write or denial-of-service effects.

Impact

This is a genuine but moderate-priority information-disclosure flaw (CWE-552) in Otter Wiki, not a high-CVSS/low-real-risk artifact. The provided CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) describes network-reachable, low-complexity exploitation with no privileges or user interaction, and the description confirms the mechanism: under the default configuration anonymous users can edit pages, so PR:N is justified by the product's default state rather than contradicted by the text. Impact is deliberately scoped as VC:L / C-only (VI:N, VA:N) because the flaw reads repository-internal files but does not write or crash - however the concrete payload (/.git/config) can expose stored git remote credentials, which can be a stepping stone to further compromise, so the Low confidentiality rating arguably understates downstream consequence. No EPSS score, KEV listing, or POC/exploit-code reference is present in the input; exploitation status is therefore 'no public exploit identified at time of analysis.' The vuln.today decision label is 'this_month' (not act_now/emergency), consistent with a patched, credentialed-impact bug that is not confirmed as actively exploited. Net: patch within the vendor/decision-label window; the main risk driver is the trivial trigger against instances that allow anonymous or low-privilege page editing.

Exploit ScenarioDerived

On an Otter Wiki instance running a vulnerable version (2.20.1 up to before 2.26.2) with the default configuration that permits anonymous page editing, an unauthenticated attacker creates or edits a page containing a DataTable embedding whose src is set to an absolute path such as /.git/config. When the page is rendered, the server reads that repository-internal file and displays its contents as a table, disclosing stored git remote credentials. No public exploit code is referenced in the available data, but the trigger is simple and fully described in the vendor's commit and tests.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Nov 02, 2026

Repository-internal file disclosure in Otter Wiki 2.20.1 through 2.26.1 lets anyone who can edit a wiki page read files stored inside the application's own repository - most critically .git/config, which frequently holds remote URLs with embedded credentials - by passing an absolute src (for example /.git/config) to the DataTable embedding, which resolves the path and renders the file contents as a table. Under the default configuration anonymous visitors can edit pages, so the CVSS vectors carry PR:N and no account is needed; instances that disable anonymous editing or restrict edit rights require a valid account with edit permission instead. Impact is bounded to reading repository-internal files (confidentiality only, no write or denial-of-service effect), scoring 6.9 under CVSS 4.0 and 5.3 under the assessed CVSS 3.1 vector; there is no CISA KEV listing and no public exploit identified at time of analysis, while a vendor fix is available in 2.26.2.

RemediationAI

Vendor-released patch: upgrade to Otter Wiki 2.26.2 (https://github.com/redimp/otterwiki/releases/tag/v2.26.2), which incorporates the fix in commit 263cac4981f60d92c46adf6386591cf4bc4d6835; the patch blocks absolute and symlinked paths into the repository's .git directory, adds case-insensitive normalization of the .git component, and routes file existence checks through the storage layer so unsafe paths are rejected before any read. Where an immediate upgrade is not possible, the practical exposure reduction is to disable anonymous page editing (or otherwise restrict edit rights to trusted accounts) so that the src-bearing page cannot be authored by an unauthenticated party; per the assessment this does not repair the underlying path handling and leaves the flaw reachable for any authenticated user with edit permission, so it is a stopgap only. Because the leaked material is typically .git/config containing remote URLs with embedded tokens, operators who ran an affected version with anonymous editing enabled should treat stored git remote credentials as potentially exposed, rotate them, and review access logs for page views containing /.git or /.GIT paths. The full VulnCheck advisory is at https://www.vulncheck.com/advisories/an-otter-wiki-2.20.1-before-2.26.2-repository-file-disclosure-via-datatable-src.

Affected VersionsENISA

otterwiki 2.20.1 <2.26.2

Affected Packages

euvd otterwiki fix: 2.26.2

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw is CWE-552 (files and directories external to the intended access scope being reachable). Otter Wiki stores page content and attachments on disk alongside a git repository, and the DataTable embedding accepts a src parameter that the server resolves to a filesystem path and parses as CSV to build an HTML table. Because an absolute src was accepted and only ordinary path resolution happened, /.git/config (and any other file under the repository root) could be read and reflected back in the rendered page. The upstream fix in commit 263cac4981f60d92c46adf6386591cf4bc4d6835 hardens three distinct cases rather than a single code path: it lowercases both the .git directory component and the resolved path before the os.path.commonpath containment check in otterwiki/gitstorage.py, so a case-insensitive filesystem cannot treat .GIT as something distinct from .git; it changes otterwiki/wiki.py to route existence checks through storage.exists(self.filepath) so unsafe paths are rejected before any filesystem probe; and it covers symlinks (for instance a link pushed through git) that point into the .git directory. An accompanying regression test also shows the ImageFrame embedding previously acted as an existence oracle for files under .git, and that the attachment lookup now refuses any spelling of .git, including ../.GIT/config. The trigger as demonstrated requires a page-editing capability plus the DataTable embedding; the exact parsing path for other embeds is not described in the available sources.

Know when Otterwiki gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulnCheck) PRIMARY 6.9 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
vuln.today AI 5.3 MEDIUM

Default config lets anonymous users edit pages (PR:N, AC:L, AV:N); impact is read-only disclosure of repository-internal files, so C:L and I:A:N.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

An Otter Wiki 2.20.1 before 2.26.2 contains a file disclosure vulnerability in the DataTable embedding that allows attackers who can edit pages, including anonymous users under the default configuration, to read repository-internal files. Attackers can set an absolute src such as /.git/config to render the file as a table, exposing any stored remote credentials.

Threat Intelligence Overview

EPSS Score
0.3%
Top 78% exploitable
Prevalence
Low
niche self-hosted open-source wiki, limited enterprise footprint
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact· derived
Medium

Priority Score

34
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +34
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy