CVE-2026-46513

Frogman: API tokens stored in plaintext

Published Jul 16, 2026 CVSS 3.1 · 7.4 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

Frogman stored API tokens directly in the database, using raw hex strings generated by random_bytes. The authentication routine compared the X‑Frogman‑Token header with this stored value, allowing an attacker who can read the oc_api_tokens table to recover active tokens that may have admin or elevated permissions. This flaw results in a violation of confidentiality and privilege escalation (CWE‑256).

Affected Systems

The vulnerability affects the Frogman PBX control software developed by mwtcmi, specifically versions prior to 1.6.2. The fix was released in v1.6.2, with v1.6.1 still vulnerable.

Risk and Exploitability

Based on the description, it is inferred that the most likely attack vector is through database read access, as the flaw requires an attacker to read the oc_api_tokens table to retrieve stored plain‑text tokens – a privilege available only to users with database credentials or to those who can compromise the system. Once a token is obtained, the attacker can replay it via the X‑Frogman‑Token header to gain the permissions originally granted to that token, including administrative rights. The CVSS score of 7.4 indicates a high severity, the EPSS score is less than 1% suggesting current exploitation probability is very low, and the vulnerability is not listed in the CISA KEV catalog.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the 1.6.2 or later release of Frogman.
  • After upgrading, revoke all pre‑upgrade tokens and issue new tokens to ensure no compromised tokens remain.
  • Limit database access to trusted administrators and enforce least‑privilege policies.

Generated by OpenCVE AI on July 31, 2026 at 01:29 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Mwtcmi
Mwtcmi frogman
Vendors & Products Mwtcmi
Mwtcmi frogman
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.
Title Frogman: API tokens stored in plaintext
Weaknesses CWE-256
References
Metrics cvssV3_1

{'score': 7.4, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N'}

Weaknesses
  • CWE-256

    Plaintext Storage of a Password

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jul 17, 2026, 1:58 PM
Reserved
May 14, 2026, 7:12 PM
Status
Deferred
Published
Jul 16, 2026, 7:16 PM
Modified
Oct 24, 2026, 8:10 PM