Account reactivation via unchecked API authorization
Published Jan 14, 2023 · Updated Apr 7, 2025
Incorrect authorization in Firefly III before 5.8.0 allows remote authenticated users to retain API access and unblock accounts. The API authentication middleware failed to reject blocked users, while the user-update controller accepted blocked-state fields from non-owner accounts. A valid user or API credential is required; exploitation restores a blocked account's access and changes its authorization state.
Summary
What happened
Incorrect authorization in Firefly III before 5.8.0 allows remote authenticated users to retain API access and unblock accounts. The API authentication middleware failed to reject blocked users, while the user-update controller accepted blocked-state fields from non-owner accounts. A valid user or API credential is required; exploitation restores a blocked account's access and changes its authorization state.
The record
- CVE
- CVE-2023-0298
- Published
- Jan 14, 2023
- Updated
- Apr 7, 2025
- Vendor
- Firefly III
- Product
- Firefly III
- Classifications
- CWE-863, T1098
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 14, 2023CVE publishedPublication date reported by the CVE source.
- Apr 7, 2025Record 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=unspecified <5.8.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.
Public exploit references
- Huntr authorization-bypass proof of conceptproof of concept · unverified
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