{"answers":{"affected":"2 open source packages ship an affected version, including @budibase/server.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73304 exists.","fix":"Upgrade @budibase/server to 3.39.25 or later.","what":"CVE-2026-73304 is a medium-severity vulnerability in budibase, published on 13 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-73304 and fix it if it is affected.\n\nWhat it is: CVE-2026-73304 is a medium-severity vulnerability in budibase, published on 13 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73304 exists.\n\nAffected packages and fixed versions:\n- @budibase/server (npm): affected all versions; fixed in 3.39.25\n- @budibase/server (npm): affected all versions; fixed in 3.39.25\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-73304/ (Markdown: https://insights.sbomify.com/CVE-2026-73304/index.md)","id":"CVE-2026-73304","markdown":"https://insights.sbomify.com/CVE-2026-73304/index.md","name":"CVE-2026-73304","record":{"aliases":["GHSA-fcrw-f7gg-6g9f"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Budibase low-code platform","requires_auth":"high_privilege","summary":"Power-role users can retrieve SSO OAuth2 tokens from user metadata endpoints, enabling persistent access to connected services.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Budibase is an open-source low-code platform. Prior to 3.39.25, GET /api/users/metadata and GET /api/users/metadata/:id returned user objects processed by packages/server/src/utilities/global.ts without removing oauth2.accessToken or oauth2.refreshToken. A user with the POWER role could retrieve the identity-provider credentials of SSO-authenticated users and use the refresh tokens for persistent access to connected services. This issue is fixed in version 3.39.25.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Budibase: SSO OAuth2 Token Leakage via User Metadata Endpoints to Power-Role Users","id":"CVE-2026-73304","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"Budibase: Privilege escalation via public role assignment API missing app-level authorization","id":"CVE-2026-73305"},"packages":[{"ecosystem":"npm","fixed":["3.39.25"],"introduced":["0"],"last_affected":[],"package":"@budibase/server","purl":null,"source":"GHSA-fcrw-f7gg-6g9f"},{"ecosystem":"npm","fixed":["3.39.25"],"introduced":["0"],"last_affected":[],"package":"@budibase/server","purl":"pkg:npm/%40budibase/server","source":"GHSA-fcrw-f7gg-6g9f"}],"prev":{"headline":"Budibase: Email Change IDOR via POST /api/v2/email allows full Account Takeover (accountId not validated against session)","id":"CVE-2026-73303"},"products":["budibase"],"published":"2026-08-13","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-14","vendors":["Budibase"]},"summary":"Power-role users can retrieve SSO OAuth2 tokens from user metadata endpoints, enabling persistent access to connected services.","url":"https://insights.sbomify.com/CVE-2026-73304/"}