Unauthorized portfolio tag modification via unchecked impersonation permissions
Published Jul 7, 2026 · Updated Sep 24, 2026
Missing authorization in Ghostfolio 3.6.0 and earlier allows remote authenticated users to modify portfolio holding tags. The updateHoldingTags path passes the Impersonation-Id value through validateImpersonationId without checking the Access.permissions field before updateTags writes the grantor's records. A valid read-only share grant is required, and exploitation can assign or remove tags, corrupting portfolio categorization, filters, and reports.
Summary
What happened
Missing authorization in Ghostfolio 3.6.0 and earlier allows remote authenticated users to modify portfolio holding tags. The updateHoldingTags path passes the Impersonation-Id value through validateImpersonationId without checking the Access.permissions field before updateTags writes the grantor's records. A valid read-only share grant is required, and exploitation can assign or remove tags, corrupting portfolio categorization, filters, and reports.
The record
- CVE
- CVE-2026-59709
- Published
- Jul 7, 2026
- Updated
- Sep 24, 2026
- Vendor
- Ghostfolio
- Product
- Ghostfolio
- Classifications
- CWE-862, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 7, 2026CVE publishedPublication date reported by the CVE source.
- Sep 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=3.6.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Public exploit references
- GitHub issue 7196 HTTP request reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started