CVE-2026-46513: CWE-256: Plaintext Storage of a Password in mwtcmi frogman
Frogman, a headless PBX control system, stored API tokens as plaintext hexadecimal strings in its database prior to version 1.6.2. These tokens, generated by a random byte function and stored without encryption, could be read directly from the database, allowing an attacker with database read access to reuse active tokens at their assigned permission level, including administrative access. This vulnerability is identified as CWE-256 and has a CVSS 3.1 score of 7.4 (high severity). The issue is fixed in Frogman version 1.6.2.
AI Analysis
Technical Summary
CVE-2026-46513 describes a vulnerability in mwtcmi Frogman versions prior to 1.6.2 where API tokens generated by Tools/CreateApiToken.php were stored as raw bin2hex(random_bytes(32)) strings in the oc_api_tokens database table. Authentication via the X-Frogman-Token HTTP header compared the token directly to these stored plaintext values. This design allowed any actor with read access to the database to recover reusable active tokens, including those with administrative privileges, thereby compromising confidentiality and integrity. The vulnerability is classified under CWE-256 (Plaintext Storage of a Password). The issue is resolved in version 1.6.2.
Potential Impact
An attacker who gains read access to the Frogman database can retrieve active API tokens stored in plaintext form. These tokens can be reused to authenticate API requests with the same permissions as the token holder, including administrative privileges. This leads to a high impact on confidentiality and integrity of the system. There is no indication of availability impact. No known exploits are reported in the wild.
Mitigation Recommendations
This vulnerability is fixed in Frogman version 1.6.2. Users should upgrade to version 1.6.2 or later to remediate this issue. Since no official patch link or vendor advisory is provided, verify the upgrade from the official Frogman sources. Until upgraded, restrict database read access to trusted users only to mitigate token exposure risk.
CVE-2026-46513: CWE-256: Plaintext Storage of a Password in mwtcmi frogman
Description
Frogman, a headless PBX control system, stored API tokens as plaintext hexadecimal strings in its database prior to version 1.6.2. These tokens, generated by a random byte function and stored without encryption, could be read directly from the database, allowing an attacker with database read access to reuse active tokens at their assigned permission level, including administrative access. This vulnerability is identified as CWE-256 and has a CVSS 3.1 score of 7.4 (high severity). The issue is fixed in Frogman version 1.6.2.
CVSS v3.1
Score 7.4high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-46513 describes a vulnerability in mwtcmi Frogman versions prior to 1.6.2 where API tokens generated by Tools/CreateApiToken.php were stored as raw bin2hex(random_bytes(32)) strings in the oc_api_tokens database table. Authentication via the X-Frogman-Token HTTP header compared the token directly to these stored plaintext values. This design allowed any actor with read access to the database to recover reusable active tokens, including those with administrative privileges, thereby compromising confidentiality and integrity. The vulnerability is classified under CWE-256 (Plaintext Storage of a Password). The issue is resolved in version 1.6.2.
Potential Impact
An attacker who gains read access to the Frogman database can retrieve active API tokens stored in plaintext form. These tokens can be reused to authenticate API requests with the same permissions as the token holder, including administrative privileges. This leads to a high impact on confidentiality and integrity of the system. There is no indication of availability impact. No known exploits are reported in the wild.
Mitigation Recommendations
This vulnerability is fixed in Frogman version 1.6.2. Users should upgrade to version 1.6.2 or later to remediate this issue. Since no official patch link or vendor advisory is provided, verify the upgrade from the official Frogman sources. Until upgraded, restrict database read access to trusted users only to mitigate token exposure risk.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-14T19:12:32.754Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a59206068715ace437c3f01
Added to database: 07/16/2026, 18:18:08 UTC
Last enriched: 07/23/2026, 22:45:20 UTC
Last updated: 08/29/2026, 22:52:11 UTC
Views: 92
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.