File-link deletion and metadata disclosure via unscoped IDs
Published Jul 30, 2026 · Updated Jul 30, 2026
Improper access control in OpenProject before 17.6.0 allows remote authenticated users to delete or re-parent file links via API. The work-package update path omits the file-link management check, while its setter resolves Storages::FileLink records by raw, globally unscoped IDs. Possession of edit_work_packages without manage_file_links is sufficient to hard-delete attached links or move another project's link and read its filename, origin ID, and MIME type.
Summary
What happened
Improper access control in OpenProject before 17.6.0 allows remote authenticated users to delete or re-parent file links via API. The work-package update path omits the file-link management check, while its setter resolves Storages::FileLink records by raw, globally unscoped IDs. Possession of edit_work_packages without manage_file_links is sufficient to hard-delete attached links or move another project's link and read its filename, origin ID, and MIME type.
The record
- CVE
- CVE-2026-67527
- Published
- Jul 30, 2026
- Updated
- Jul 30, 2026
- Vendor
- OpenProject GmbH
- Product
- OpenProject
- Classifications
- T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 30, 2026CVE publishedPublication date reported by the CVE source.
- Jul 30, 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=< 17.6.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo