CVE-2025-67084
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedFile upload vulnerability in InvoicePlane through 1.6.3 allows authenticated attackers to upload arbitrary PHP files into attachments, which can later be executed remotely, leading to Remote Code Execution (RCE).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceInvoicePlane 1.6.3 and earlier contains a file upload vulnerability in its attachments feature that allows authenticated users to upload arbitrary PHP files. These malicious files can then be accessed and executed remotely, enabling complete remote code execution on the affected server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.6.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify InvoicePlane installation and versionLocate the InvoicePlane installation on your server and check the version number in the application (typically visible in the admin panel under System Info or in a version file within the application root)Affected if The installed version is 1.6.3 or earlier (any version below 1.6.4)
-
Confirm authenticated user access existsReview your user management settings to determine if there are any user accounts with access to the InvoicePlane systemAffected if There are active user accounts that can log in to InvoicePlane
-
Verify the attachments upload feature is accessibleLog in as an authenticated user and navigate to the attachments or file upload functionality within InvoicePlane (typically found when creating or editing invoices, quotes, or clients)Affected if The attachments upload feature is enabled and accessible to authenticated users
-
Check PHP execution settings in uploads directoryInspect the server configuration and the directory where InvoicePlane stores uploaded files (usually the uploads folder). Verify if PHP execution is permitted in this directory by reviewing .htaccess rules or web server configurationAffected if PHP files can be executed from the attachments or uploads directory
You are affected if InvoicePlane version is below 1.6.4, authenticated users can access the attachments upload feature, and PHP execution is allowed in the uploads directory.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.6.4
Update InvoicePlane to a patched version beyond 1.6.3. As an interim measure, disable PHP execution in the attachments directory and restrict upload permissions to prevent authenticated users from uploading executable file types.
1.6.4
- Backup your InvoicePlane installation and database before upgrading
- Download InvoicePlane version 1.6.4 from the official InvoicePlane repository
- Replace the existing InvoicePlane files with the 1.6.4 release files, preserving your configuration and database connection settings
- Verify the upgrade was successful by logging in and checking the version number
- Test file upload functionality to confirm the vulnerability is patched
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67084 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-67084 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data