{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-46513 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-46513 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-46513 is a high-severity vulnerability in mwtcmi frogman, published on 16 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-46513 and fix it if it is affected.\n\nWhat it is: CVE-2026-46513 is a high-severity vulnerability in mwtcmi frogman, published on 16 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-46513 in the wild and no public exploit code.\n\nAffected product: mwtcmi frogman. 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-46513/ (Markdown: https://insights.sbomify.com/CVE-2026-46513/index.md)","id":"CVE-2026-46513","markdown":"https://insights.sbomify.com/CVE-2026-46513/index.md","name":"CVE-2026-46513","record":{"aliases":["GHSA-9xf5-9ghq-p6cw"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"PBX control software","requires_auth":"none","summary":"Attackers with database access can recover plaintext API tokens to gain unauthorized control over the PBX system.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-256","name":"Plaintext Storage of a Password"}],"description":"Frogman provides headless PBX control through MCP and HTTP API. Prior to 1.6.2, Frogman stored API tokens generated by Tools/CreateApiToken.php:33-36 as raw bin2hex(random_bytes(32)) strings in oc_api_tokens, and Frogman.class.php:78 authenticated the X-Frogman-Token header by comparing it with the stored raw value, allowing database read access to recover reusable active tokens at their assigned permission level, including admin. This issue is fixed in version 1.6.2.","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":"Frogman: API tokens stored in plaintext","id":"CVE-2026-46513","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Frogman: Plaintext passwords and secrets persisted to audit log","id":"CVE-2026-46514"},"packages":[],"prev":{"headline":"Frogman: Dialplan template parameters interpolated into extensions_custom.conf without escaping","id":"CVE-2026-46512"},"products":["frogman"],"published":"2026-07-16","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-17","vendors":["mwtcmi"]},"summary":"Attackers with database access can recover plaintext API tokens to gain unauthorized control over the PBX system.","url":"https://insights.sbomify.com/CVE-2026-46513/"}