{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-53642 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-53642 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-53642 is a medium-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-53642 and fix it if it is affected.\n\nWhat it is: CVE-2026-53642 is a medium-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-53642 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-53642/ (Markdown: https://insights.sbomify.com/CVE-2026-53642/index.md)","id":"CVE-2026-53642","markdown":"https://insights.sbomify.com/CVE-2026-53642/index.md","name":"CVE-2026-53642","record":{"aliases":["GHSA-7v47-rh46-w923"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Billing management system","requires_auth":"low_privilege","summary":"Unverified clients can access sensitive account data in FOSSBilling when email confirmation is enabled, exposing balances and transaction history.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"FOSSBilling is a free, open-source billing and client management system. In versions 0.5.6 through 0.7.2, when the \"Require Email Confirmation\" setting is enabled, a logged-in client with an unverified email address (`email_approved = 0`) can access all client-area pages (e.g. `/client/balance`, `/client/order/list`, `/client/invoice`) and read real account data, including wallet balances and transaction history. The API-side enforcement correctly restricts unverified clients to only profile-related endpoints, but the page-side enforcement is overly permissive, allowing any request whose path starts with `/client`. Version 0.8.0 contains a fix. No known workarounds that don't involve modifying the source code are available.","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: Unverified clients can access client-area pages when email confirmation is required","id":"CVE-2026-53642","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 allows low-privileged staff accounts to perform unauthorized actions via admin API endpoints","id":"CVE-2026-53643"},"packages":[],"prev":{"headline":"FOSSBilling has stored XSS in client email views via unescaped content in JavaScript template literal","id":"CVE-2026-53641"},"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":"partial"},"state":"PUBLISHED","updated":"2026-07-07","vendors":["FOSSBilling"]},"summary":"Unverified clients can access sensitive account data in FOSSBilling when email confirmation is enabled, exposing balances and transaction history.","url":"https://insights.sbomify.com/CVE-2026-53642/"}