CVE Feed

    Dashboard / CVE / CVE-2025-48925

    CVE-2025-48925

    The TeleMessage service through 2025-05-05 relies on the client side (e.g., the TM SGNL app) to do MD5 hashing, and then accepts the hash as the authentication credential.

    Published:May 28, 2025
    Last Modified:Oct 22, 2025
    EPS:May 28, 2025
    EPSS Score:0.00074
    CVSS Score:4.3

    Affected Products

    Vendor
    Smarsh
    Product
    Telemessage

    Exploits

    No exploit reference

    Related CVEs

    CVE-2025-48931 (CVSS 3.2) — The TeleMessage service through 2025-05-05 relies on MD5 for password hashing, which opens up various attack p…
    CVE-2025-48928 (CVSS 4) — The TeleMessage service through 2025-05-05 is based on a JSP application in which the heap content is roughly …
    CVE-2025-48927 (CVSS 5.3) — The TeleMessage service through 2025-05-05 configures Spring Boot Actuator with an exposed heap dump endpoint …
    CVE-2025-48926 (CVSS 4.3) — The admin panel in the TeleMessage service through 2025-05-05 allows attackers to discover usernames, e-mail a…
    CVE-2025-48929 (CVSS 4) — The TeleMessage service through 2025-05-05 implements authentication through a long-lived credential (e.g., no…
    CVE-2025-48930 (CVSS 2.8) — The TeleMessage service through 2025-05-05 stores certain cleartext information in memory, even though memory …
    CVE-2025-47730 (CVSS 4.8) — The TeleMessage archiving backend through 2025-05-05 accepts API calls (to request an authentication token) fr…

    Common Vulnerability Scoring System

    Attack Vector
    Network
    Adjacent
    Local
    Physical
    Privileges Required
    None
    Low
    High
    User Interaction
    None
    Required
    Scope
    Unchanged
    Changed
    Confidentiality
    None
    Low
    High
    Integrity
    None
    Low
    High
    Availability
    None
    Low
    High