Credential disclosure and reset via missing state checks
Published Jul 6, 2026 · Updated Jul 6, 2026
Authorization bypass in FOSSBilling 0.5.3 through 0.7.2 allows remote authenticated users to read and reset API key secrets. The client order service path returns api_key without calling isActive(), while resetApiKey() checks ownership but generates and stores a new key without checking the related order state. Exploitation requires a client-owned, non-active API-key order and exposes or rotates the credential trusted by downstream systems.
Summary
What happened
Authorization bypass in FOSSBilling 0.5.3 through 0.7.2 allows remote authenticated users to read and reset API key secrets. The client order service path returns api_key without calling isActive(), while resetApiKey() checks ownership but generates and stores a new key without checking the related order state. Exploitation requires a client-owned, non-active API-key order and exposes or rotates the credential trusted by downstream systems.
The record
- CVE
- CVE-2026-53644
- Published
- Jul 6, 2026
- Updated
- Jul 6, 2026
- Vendor
- FOSSBilling
- Product
- FOSSBilling
- Classifications
- CWE-639, T1552
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 6, 2026CVE publishedPublication date reported by the CVE source.
- Jul 6, 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.5.3, < 0.8.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