What is the CVSS score of CVE-2025-67083?

CVE-2025-67083 has a CVSS 3.1 base score of 5.3 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N. EPSS exploitation probability: 0.1%.

Which versions of Invoiceplane are affected by CVE-2025-67083?

Organizations using InvoicePlane should be aware of moderate risk from CVE-2025-67083, a path traversal vulnerability rated CVSS 5.3. This could allow unauthorized file access.

Is there a public PoC exploit available for CVE-2025-67083?

Yes, a public proof-of-concept exploit is available for CVE-2025-67083. Prioritise patching immediately. EPSS: 0.1%.

How to fix or mitigate CVE-2025-67083?

Within 30 days: Identify affected systems running InvoicePlane and apply vendor patches as part of regular patch cycle. Review file handling controls.

Invoiceplane CVE-2025-67083

MEDIUM

Path Traversal (CWE-22)

2026-01-15 cve@mitre.org

Path Traversal Invoiceplane

5.3

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

5.3 MEDIUM

AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Lifecycle Timeline

Analysis Generated

Mar 12, 2026 - 21:54 vuln.today

PoC Detected

Jan 22, 2026 - 16:03 vuln.today

Public exploit code

CVE Published

Jan 15, 2026 - 15:15 nvd

MEDIUM 5.3

DescriptionCVE.org

Directory traversal vulnerability in InvoicePlane through 1.6.3 allows unauthenticated attackers to read files from the server. The ability to read files and the file type depends on the web server and its configuration.

AnalysisAI

Technical ContextAI

Classified as CWE-22 (Path Traversal). Affects Invoiceplane. Directory traversal vulnerability in InvoicePlane through 1.6.3 allows unauthenticated attackers to read files from the server. The ability to read files and the file type depends on the web server and its configuration.

RemediationAI

Monitor vendor advisories for a patch. Validate and sanitize file path inputs. Use allowlists. Restrict network access to the affected service where possible.