{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-53644 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-53644 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-53644 is a high-severity missing authorization vulnerability in FOSSBilling, published on 6 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-53644 and fix it if it is affected.\n\nWhat it is: CVE-2026-53644 is a high-severity missing authorization vulnerability in FOSSBilling, published on 6 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-53644 in the wild and no public exploit code.\n\nAffected product: FOSSBilling. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-53644/ (Markdown: https://insights.sbomify.com/CVE-2026-53644/index.md)","id":"CVE-2026-53644","markdown":"https://insights.sbomify.com/CVE-2026-53644/index.md","name":"CVE-2026-53644","record":{"aliases":["GHSA-qf6j-vq68-qmfh"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Billing management system","requires_auth":"low_privilege","summary":"Authenticated clients can read and reset API key secrets for inactive orders due to missing state validation in FOSSBilling.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"FOSSBilling is a free, open-source billing and client management system. Versions 0.5.3 through 0.7.2 allow authenticated clients to both read and reset API key service secrets for orders that are no longer in an `active` state (e.g., `suspended`, `canceled`). The root cause is missing order-state validation in two client API endpoints, despite an `isActive()` helper already existing in the `Serviceapikey` module and the frontend UI correctly gating access on `order.status == 'active'`. Version 0.8.0 contains a fix. Some workarounds are available. If the `Serviceapikey` module is not needed, uninstall it to remove the affected endpoints. One may also use a reverse proxy or WAF to restrict access to `/api/client/order/service` and `/api/client/serviceapikey/reset` based on application-level order-state logic.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"FOSSBilling's missing order-state validation allows clients to read and reset API key secrets for non-active orders","id":"CVE-2026-53644","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"FOSSBilling's missing self-edit prevention in staff permission management allows persistent privilege escalation","id":"CVE-2026-53645"},"packages":[],"prev":{"headline":"FOSSBilling allows low-privileged staff accounts to perform unauthorized actions via admin API endpoints","id":"CVE-2026-53643"},"products":["FOSSBilling"],"published":"2026-07-06","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-07","vendors":["FOSSBilling"]},"summary":"Authenticated clients can read and reset API key secrets for inactive orders due to missing state validation in FOSSBilling.","url":"https://insights.sbomify.com/CVE-2026-53644/"}