{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-46516 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-46516 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-46516 is a medium-severity cross-site scripting vulnerability in mwtcmi frogman, published on 20 Jul 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-46516 and fix it if it is affected.\n\nWhat it is: CVE-2026-46516 is a medium-severity cross-site scripting vulnerability in mwtcmi frogman, published on 20 Jul 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-46516 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-46516/ (Markdown: https://insights.sbomify.com/CVE-2026-46516/index.md)","id":"CVE-2026-46516","markdown":"https://insights.sbomify.com/CVE-2026-46516/index.md","name":"CVE-2026-46516","record":{"aliases":["GHSA-7qvv-vgw9-rcxg"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"FreePBX control tool","requires_auth":"high_privilege","summary":"Stored XSS in Frogman chat console allows attackers to execute scripts in admin sessions via unescaped user-controlled fields.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Frogman provides headless FreePBX control. Prior to version 1.6.6, Frogman's chat-console markdown formatter (`assets/js/chat.js`'s `formatMarkdown`) inserted regex capture groups as raw HTML in four template patterns: inline code, bold, markdown links, and download links. Tool responses that reflect user-controlled fields — extension names, ring-group descriptions, IVR names, queue descriptions, etc. — could carry an HTML/JavaScript payload that executes when another admin views the response through Frogman chat. The payload runs in the viewer's session, with the viewer's permissions. FreePBX's own admin GUI escapes these same fields via `freepbx_htmlspecialchars()` throughout its view templates. The chat formatter was the leaky side. Version 1.6.6 patches the issue.","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 vulnerable to stored XSS in chat console formatter (escalation vector in multi-admin deployments)","id":"CVE-2026-46516","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"LMDeploy: Hardcoded trust_remote_code=True is an implicit unsafe remote-code load path with no user opt-out","id":"CVE-2026-46517"},"packages":[],"prev":{"headline":"Frogman: Multiple read-tier tools expose admin-grade data and arbitrary GraphQL execution","id":"CVE-2026-46515"},"products":["frogman"],"published":"2026-07-20","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-20","vendors":["mwtcmi"]},"summary":"Stored XSS in Frogman chat console allows attackers to execute scripts in admin sessions via unescaped user-controlled fields.","url":"https://insights.sbomify.com/CVE-2026-46516/"}