Frogman provides headless PBX control through MCP and HTTP API. Prior to 1.6.2, fm_reset_password in Tools/ResetPassword.php:48-53 returned a plaintext password and fm_add_extension in Tools/AddExtension.php:172 returned a plaintext secret; Frogman.class.php:2207-2211 used auditOutcome to JSON-encode those responses into oc_audit_log.detail, allowing any PERM_READ caller with access to fm_audit_search to recover the stored credentials. This issue is fixed in version 1.6.2.
CVE-2026-46514
This medium-severity CVE scores 6.5 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).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(medium)
- EG Risk
- 29(Track)EG Risk 29/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 computedSeverity65% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 17.6%
- KEV
- Not listed
Published
July 16, 2026
Last Modified
July 17, 2026
Advisory Details (1)
Auto-updated Jul 16, 2026Plaintext passwords and secrets persisted to audit log · Advisory · mwtcmi/frogman · GitHub
https://github.com/mwtcmi/frogman/security/advisories/GHSA-3p65-2prr-cfvfWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 12× 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.
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:17 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:34 UTCEG score recompute
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 18:19 UTCEG score recompute
- 2026-07-16 18:18 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-532
- CVE-2016-0898EG 10.0CRITICAL
- CVE-2018-17922EG 9.8CRITICAL
- CVE-2018-1264NVD 9.1EG 9.8CRITICAL
- CVE-2018-16049EG 9.8CRITICAL
- CVE-2018-11717EG 9.8EPSS 95%CRITICAL
- CVE-2018-11716EG 9.8EPSS 96%CRITICAL
- CVE-2018-0042EG 9.8CRITICAL
- CVE-2018-1072NVD 5.0EG 9.8MEDIUM
- CVE-2018-1117NVD 5.0EG 9.8MEDIUM
- CVE-2018-11320EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-46514?
When was CVE-2026-46514 disclosed?
Is CVE-2026-46514 actively exploited?
What is the CVSS score of CVE-2026-46514?
How do I remediate CVE-2026-46514?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-46514
Is Your Infrastructure Affected by CVE-2026-46514?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.