{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-73661 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-73661 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-73661 is a high-severity authentication bypass vulnerability in Sangoma Freepbx, published on 13 Aug 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-73661 and fix it if it is affected.\n\nWhat it is: CVE-2026-73661 is a high-severity authentication bypass vulnerability in Sangoma Freepbx, published on 13 Aug 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-73661 in the wild and no public exploit code.\n\nAffected product: Sangoma Freepbx. 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-73661/ (Markdown: https://insights.sbomify.com/CVE-2026-73661/index.md)","id":"CVE-2026-73661","markdown":"https://insights.sbomify.com/CVE-2026-73661/index.md","name":"CVE-2026-73661","record":{"aliases":["GHSA-f6hc-rqxg-ch86"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"IP PBX system","requires_auth":"low_privilege","summary":"An authenticated attacker can restore a crafted backup to disable FreePBX authentication, bypassing security controls and potentially gaining unauthorized access.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"freepbx","vendor":"sangoma"}],"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-15","name":"External Control of System or Configuration Setting"}],"description":"FreePBX is an open source IP PBX. Prior to 16.0.47 and 17.0.30, the FreePBX Framework module permits a crafted backup to restore the hidden AUTHTYPE setting with the value none through runRestore() in amp_conf/htdocs/admin/libraries/Builtin/Restore.php. An authenticated user with sufficient backup-restore access or write access to backup files can thereby disable FreePBX authentication during restoration, bypassing the user-interface removal of AUTHTYPE=none. This issue is fixed in versions 16.0.47 and 17.0.30.","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":"FreePBX: Authenticated Framework AUTHTYPE Can Be Restored From a Crafted Backup","id":"CVE-2026-73661","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"sangoma:freepbx","products":["sangoma:freepbx"],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Authenticated FreePBX Music RCE via mpg123 and Asterisk Call Files","id":"CVE-2026-73662"},"packages":[],"prev":{"headline":"FreePBX: Authenticated TTS AGI Command Injection Through TTS Name","id":"CVE-2026-73660"},"products":["framework"],"published":"2026-08-13","related":[{"cvss_score":10,"headline":"Sangoma FreePBX Authentication Bypass","id":"CVE-2025-57819","kev_date_added":"2025-08-29","published":"2025-08-28"},{"cvss_score":9.8,"headline":"Sangoma FreePBX Improper Authentication","id":"CVE-2019-19006","kev_date_added":"2026-02-03","published":"2019-11-21"},{"cvss_score":9.3,"headline":"FreePBX: Unauthenticated SQL injection in FreePBX missedcall via inbound Caller ID name leads to administrator takeover","id":"CVE-2026-73663","kev_date_added":null,"published":"2026-08-13"},{"cvss_score":9.3,"headline":"FreePBX UCP: Unauthenticated remote code execution via socket.io namespace auth bypass and AMI action injection","id":"CVE-2026-73665","kev_date_added":null,"published":"2026-08-13"},{"cvss_score":9.3,"headline":"FreePBX: Unauthenticated Use of Hard-Coded Credentials Vulnerability in FreePBX UCP Interface","id":"CVE-2026-46376","kev_date_added":null,"published":"2026-05-29"},{"cvss_score":9.3,"headline":"FreePBX Endpoint Manager Allows Unauthenticated Logins to Administrator Control Panel via Forged Basic Auth Header","id":"CVE-2025-66039","kev_date_added":null,"published":"2025-12-09"},{"cvss_score":8.8,"headline":"Missing authorization in n/a","id":"CVE-2023-43336","kev_date_added":null,"published":"2023-11-02"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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-08-14","vendors":["FreePBX"]},"summary":"An authenticated attacker can restore a crafted backup to disable FreePBX authentication, bypassing security controls and potentially gaining unauthorized access.","url":"https://insights.sbomify.com/CVE-2026-73661/"}