CVE-2025-48931

Published May 28, 2025
·
Updated

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 Software

2 affected components
TeleMessage TeleMessage service<=2025-05-05
Smarsh TeleMessage<=2025-05-05

Event History

May 28, 2025
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:15 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-48931?

CVE-2025-48931 has a high severity due to its reliance on MD5 for password hashing, making it vulnerable to various attacks.

2

How do I fix CVE-2025-48931?

To fix CVE-2025-48931, migrate to a stronger password hashing algorithm such as bcrypt or Argon2.

3

What software is affected by CVE-2025-48931?

CVE-2025-48931 affects the TeleMessage service up to version 2025-05-05.

4

What are the risks associated with CVE-2025-48931?

The risks associated with CVE-2025-48931 include unauthorized access and data breaches due to easily cracked passwords.

5

Are there workarounds for CVE-2025-48931?

While upgrading to a more secure hashing algorithm is the best approach, temporarily increasing password complexity can help mitigate the risk.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203