CVE-2026-46513

HIGHPre-NVD 7.47.4—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 82% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
7.4
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.4Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.4
EG Score
7.4(medium)
EG Risk
33(Track)
EG Risk 33/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity74% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
17.7%
KEV
Not listed

Published

July 16, 2026

Last Modified

July 17, 2026

Advisory Details (4)

Auto-updated Jul 16, 2026
Patch available. Sources: github_commit, github_release, github.
github Patch Available

API tokens stored in plaintext · Advisory · mwtcmi/frogman · GitHub

https://github.com/mwtcmi/frogman/security/advisories/GHSA-9xf5-9ghq-p6cw
github_release Patch Available

v1.6.2 — install.php regression fix

Patch available: mwtcmi/frogman v1.6.2

https://github.com/mwtcmi/frogman/releases/tag/v1.6.2
github_release Patch Available

v1.6.1 — Security release (superseded by v1.6.2)

Patch available: mwtcmi/frogman v1.6.1

https://github.com/mwtcmi/frogman/releases/tag/v1.6.1
github_commit Patch Available

commit b10f314add08 (mwtcmi/frogman)

Patch available: mwtcmi/frogman v1.6.1 (contains commit b10f314add08)

https://github.com/mwtcmi/frogman/commit/b10f314add08c8e7585ba4b27d071b07d026ab55

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 11× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 03:17 UTCEG score recompute
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:24 UTCEPSS rescore
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 02:34 UTCEG score recompute
  7. 2026-07-19 02:29 UTCEPSS rescore
  8. 2026-07-18 10:04 UTCEPSS rescore
  9. 2026-07-17 14:13 UTCEG score recompute
  10. 2026-07-16 18:19 UTCEG score recompute
  11. 2026-07-16 18:18 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-46513?
CVE-2026-46513 is a high vulnerability published on July 16, 2026. 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(randombytes(32)) strings in ocapi_tokens, and Frogman.class.php:78 authenticated the X-Frogman-Token header by comparing it with the…
When was CVE-2026-46513 disclosed?
CVE-2026-46513 was first published in the National Vulnerability Database on July 16, 2026, with the most recent update on July 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46513 actively exploited?
CVE-2026-46513 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 17.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46513?
CVE-2026-46513 has a CVSS v3 base score of 7.4 (NVD).
How do I remediate CVE-2026-46513?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46513, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-46513

Explore →

Is Your Infrastructure Affected by CVE-2026-46513?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs