Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach unauthenticated Paisa editor/sheet endpoint
-
ExploitSubmit file name with ../ sequences
-
ExecutionBypass journal/sheets directory confinement
-
ImpactRead arbitrary server files or delete backup files
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK
2 techniques across 2 tactics: Discovery, Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires only that a Paisa instance before v0.7.8 be reachable over the network: the GetFile/GetSheet (editor file) and DeleteBackups/DeleteSheetBackups (delete_backups) endpoints accept an attacker-controlled file name and, pre-fix, pass it directly into filepath.Join/filepath.Glob without confinement, so '../' sequences escape the journal or sheets directory. Per the CVSS vector there is no authentication (PR:N), no user interaction (UI:N) and no non-default configuration required - any default deployment is affected. The principal limiting factor is exposure: Paisa is designed as a locally run, single-user self-hosted finance tool, so realistic risk depends on the instance being bound to an interface reachable by untrusted clients rather than localhost. Read impact is bounded to files readable by the server process account; the destructive action is limited to deletion of backup (.backup.*) files. |
| Impact | The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) describes a trivially reachable flaw: network-accessible, low attack complexity, no authentication (PR:N) and no user interaction, yielding high confidentiality impact (VC:H) from arbitrary file reads plus low integrity impact (VI:L) from backup deletion. The vuln.today decision label is 'this_week' rather than act_now/emergency, and the input provides no EPSS score and no KEV listing, so there is no evidence of active exploitation or mass-scanning pressure at this time. The dominant mitigating signal is deployment footprint, not technical difficulty: Paisa is a self-hosted personal-finance (double-entry accounting) application typically run locally by a single user, so the unauthenticated network exploitability only translates into real risk where an instance has been deliberately exposed to an untrusted network. Net assessment: technically a genuine high-severity unauthenticated path traversal confirmed by the vendor patch, but its practical priority is bounded by low real-world prevalence and the absence of KEV/EPSS corroboration - treat it as a prompt patch for exposed instances rather than a widespread emergency. |
| Exploit ScenarioDerived | An attacker who can reach a network-exposed Paisa instance sends a crafted file name containing '../' sequences to the editor 'GetFile'/'GetSheet' endpoints to read any server-readable file outside the journal or sheets directory, and to the 'delete_backups' endpoints to remove backup files outside those directories. No authentication or user interaction is required per the CVSS vector. No confirmed working public exploit code is listed in the input, though a VulnCheck advisory, a GitHub issue (#420) and the fixing commit are published. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 25, 2026
Unauthenticated path traversal in Paisa before v0.7.8 lets remote attackers read arbitrary server-readable files and delete backup files by supplying '../' sequences in the file name accepted by the editor file handlers (GetFile, GetSheet) and the delete_backups handlers (DeleteBackups, DeleteSheetBackups). The flaw is rated CVSS 4.0 8.8 (AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L) and the vendor has released a fix in v0.7.8, so any default deployment reachable over the network is exposed until upgraded; no public exploit code was identified at time of analysis, and practical risk is bounded mainly by whether the instance is bound beyond localhost. Confidentiality impact is high because reads are limited only by the permissions of the server process account, while integrity impact is low and confined to removal of .backup.* files.
RemediationAI
Vendor-released patch: upgrade to Paisa v0.7.8 or later, which confines file-name resolution through utils.BuildSubPath and the new utils.Glob helper and rejects traversal attempts with an 'Invalid file name' response (fix commit 035949351f7c0d0f90ecf767aa1e28b4d5a0ae31, release notes at https://github.com/ananthakumaran/paisa/releases/tag/v0.7.8, tracking issue https://github.com/ananthakumaran/paisa/issues/420). No patched version exists for the 0.7.x branch other than 0.7.8 itself, so older builds must be replaced rather than incrementally patched. Because Paisa is designed as a locally run, single-user finance tool, the decisive compensating control while upgrading is exposure: bind the HTTP listener to localhost or place it behind a network restriction so only trusted clients can reach the editor and delete_backups endpoints, accepting that this reduces the convenience of remote access. Note that the read-only configuration flag does not mitigate the traversal, as the upstream tests demonstrate, so enabling read-only mode is not a substitute for the upgrade.
Affected VersionsENISA
Affected Packages
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
Paisa is a Go personal-finance application whose built-in editor serves ledger (.ledger) and sheet (.paisa) files through a gin-based HTTP server. Before the fix, the handlers in internal/server/editor.go and internal/server/sheet.go took the client-supplied file name and passed it straight into filepath.Join(dir, file.Name) for reads and filepath.Glob(filepath.Join(dir, file.Name+".backup.*")) for backup enumeration and deletion, with no check that the resolved path stayed beneath the configured journal or sheets directory. This is classic CWE-22 (Improper Limitation of a Pathname to a Restricted Directory): '../' segments normalise out of the base directory, so reads escape to any file the process can open and deletes can target backup files elsewhere. The fixing commit 035949351f7c0d0f90ecf767aa1e28b4d5a0ae31 introduces utils.BuildSubPath to validate and confine the constructed path and a utils.Glob helper for backup matching, returning an 'Invalid file name' response on traversal attempts. The accompanying tests exercise both the ledger and sheet APIs, both read and delete handlers, and both read-only and writable configurations, confirming that read-only mode did not prevent the traversal.
Know when Paisa 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
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N
Unauthenticated network-reachable handlers with no user interaction give AV:N/AC:L/PR:N/UI:N; arbitrary file read is C:H while backup deletion is limited integrity impact (I:L), with no availability loss.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
Paisa before 0.7.8 contains a path traversal vulnerability in the GetFile, GetSheet, DeleteBackups, and DeleteSheetBackups handlers that lets unauthenticated attackers read files and delete backups through ../ sequences in file names. Attackers can send crafted names to the editor file and delete_backups endpoints to read any server-readable file and remove backup files outside the journal or sheets directory.
Technical POC Analysis
CWE-22 (Improper Limitation of a Pathname to a Restricted Directory).
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Latest POC
2 public PoC links from nuclei
Sign in to open the public PoC links collected for this CVE.
Executive ViewAI
Paisa, a financial management application, contains a high-severity path traversal vulnerability (CVE-2026-116067) that allows unauthenticated remote attackers to read arbitrary files and delete backup files on affected servers. Any organization running a network-accessible Paisa instance prior to v0.7.8 is exposed to potential data theft, and leadership should prioritize patching to prevent unauthorized access to sensitive financial and system data.
Apply vendor patch.
Threat Model
2 threats: Information Disclosure, Tampering
5-step attack chain with trust boundaries and controls
Full threat model - attack chain, trust boundaries, controls per stage and evidence - is part of the Pro and Business plans.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.
EUVD-2026-109381
GHSA-c69r-vcvw-qgm3
NVD
CVE.org
EPSS
VulDB
Exploit-DB