What is the CVSS score of CVE-2025-48931?

CVE-2025-48931 has a CVSS 3.1 base score of 3.2 (Low). CVSS vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N. EPSS exploitation probability: 0.0%.

Which versions of Telemessage are affected by CVE-2025-48931?

CVE-2025-48931 is a low-severity vulnerability in TeleMessage service through 2025-05-05 relies on MD5 for password (CVSS 3.2).

How to fix or mitigate CVE-2025-48931?

During next maintenance window: Apply vendor patches when convenient. Monitor vendor channels for updates.

Telemessage CVE-2025-48931

LOW

Use of Weak Hash (CWE-328)

2025-05-28 cve@mitre.org

Information Disclosure Telemessage

3.2

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

3.2 LOW

AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N

Attack Vector

Local

Attack Complexity

High

Privileges Required

None

User Interaction

None

Scope

Changed

Confidentiality

Low

Integrity

None

Availability

None

Lifecycle Timeline

Analysis Generated

Mar 28, 2026 - 18:44 vuln.today

CVE Published

May 28, 2025 - 17:15 nvd

LOW 3.2

DescriptionCVE.org

The TeleMessage service through 2025-05-05 relies on MD5 for password hashing, which opens up various attack possibilities (including rainbow tables) with low computational effort.

AnalysisAI

The TeleMessage service through 2025-05-05 relies on MD5 for password hashing, which opens up various attack possibilities (including rainbow tables) with low computational effort. Rated low severity (CVSS 3.2), this vulnerability is no authentication required. No vendor patch available.

Technical ContextAI

This vulnerability is classified under CWE-328. The TeleMessage service through 2025-05-05 relies on MD5 for password hashing, which opens up various attack possibilities (including rainbow tables) with low computational effort. Affected products include: Smarsh Telemessage. Version information: through 2025.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.