{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-55739 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-55739 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-55739 is a medium-severity vulnerability in FreePBX api, published on 4 Sep 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-55739 and fix it if it is affected.\n\nWhat it is: CVE-2025-55739 is a medium-severity vulnerability in FreePBX api, published on 4 Sep 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-55739 in the wild and no public exploit code.\n\nAffected product: FreePBX api. 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-2025-55739/ (Markdown: https://insights.sbomify.com/CVE-2025-55739/index.md)","id":"CVE-2025-55739","markdown":"https://insights.sbomify.com/CVE-2025-55739/index.md","name":"CVE-2025-55739","record":{"aliases":["GHSA-3r47-p39v-vqqf"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass","privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"FreePBX API module","requires_auth":"low_privilege","summary":"Attackers can forge JWT tokens using a shared OAuth private key to bypass authentication and gain full API access in FreePBX.","user_interaction":"required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L","version":"4.0"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"},{"id":"CWE-522","name":"Insufficiently Protected Credentials"}],"description":"api is a module for FreePBX@, which is an open source GUI that controls and manages Asterisk© (PBX). In versions lower than 15.0.13, 16.0.2 through 16.0.14, 17.0.1 and 17.0.2, there is an identical OAuth private key used across multiple systems that installed the same FreePBX RPM or DEB package. An attacker with access to the shared OAuth private key could forge JWT tokens, bypass authentication, and potentially gain full access to both REST and GraphQL APIs. Systems with the \"api\" module enabled, configured and previously activated by an administrator for remote inbound connections may be affected. This issue is fixed in versions 15.0.13, 16.0.15 and 17.0.3.","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":"api: Shared OAuth Signing Key Between Different Instances","id":"CVE-2025-55739","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Default Credentials in nginx-defender Configuration Files","id":"CVE-2025-55740"},"packages":[],"prev":{"headline":"flaskBlog arbitrary comment delete","id":"CVE-2025-55737"},"products":["api"],"published":"2025-09-04","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-02-13","vendors":["FreePBX"]},"summary":"Attackers can forge JWT tokens using a shared OAuth private key to bypass authentication and gain full API access in FreePBX.","url":"https://insights.sbomify.com/CVE-2025-55739/"}