Cyber Resilience

CVE-2025-27408

Published
28 February 2025
Modified
15 April 2026
CVSS Score v3.1 4.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
EPSS Score 0.0015 5th percentile
Risk Priority 37 floored blend · peak EPSS

Summary

CVE-2025-27408 is a medium-severity Use of a One-Way Hash without a Salt (CWE-759) vulnerability. Its CVSS base score is 4.8 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Password Cracking (T1110.002); ranked at the 5th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to IA-5 (Authenticator Management) and SA-11 (Developer Testing and Evaluation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A04:2025 Cryptographic Failures

EU & UK References

Vulnerability Data

Manifest offers users a one-file micro back end. Prior to version 4.9.2, Manifest employs a weak password hashing implementation that uses SHA3 without a salt. This exposes user passwords to a higher risk of being cracked if an attacker gains…

more

access to the database. Without the use of a salt, identical passwords across multiple users will result in the same hash, making it easier for attackers to identify and exploit patterns, thereby accelerating the cracking process. Version 4.9.2 fixes the issue.

CWE(s)
CWE-759

Related Threats

MITRE ATT&CK Enterprise Techniques

T1110.002 Password Cracking Credential Access
Adversaries may use password cracking to attempt to recover usable credentials, such as plaintext passwords, when credential material such as password hashes are obtained.
attack.mitre.org →
T1110 Brute Force Credential Access
Adversaries may use brute force techniques to gain access to accounts when passwords are unknown or when password hashes are obtained.
attack.mitre.org →
T1552 Unsecured Credentials Credential Access
Adversaries may search compromised systems to find and obtain insecurely stored credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-10205Shared CWE-759
CVE-2025-36253Shared CWE-759
CVE-2023-1430Shared CWE-759
CVE-2025-53884Shared CWE-759
CVE-2026-45027Shared CWE-759
CVE-2026-9370Shared CWE-759
CVE-2023-33838Shared CWE-759
CVE-2025-34208Shared CWE-759
CVE-2024-8453Shared CWE-759
CVE-2024-36440Shared CWE-759

Affected Assets

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SC-13 Cryptographic Protection good match

Cryptographic protection requirements specify approved algorithms and usage that encompass salted one-way hashes for passwords.

IA-5 Authenticator Management good match

Authenticator management requires secure credential storage practices that include salted hashes.

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can identify missing salt values through code review or analysis.

SA-15 Development Process, Standards, and Tools partial match

Development standards and tools can mandate salted hashing as part of secure implementation requirements.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 full match
prevents

Secure SDLC practices mandate correct password storage with salts, eliminating this exact weakness.

PR.DS-01 mostly match
prevents

Proper cryptographic hashing for data-at-rest protection directly requires salted hashes for passwords.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.24 Use of cryptography mostly match
prevents

Use of cryptography requires appropriate cryptographic controls including salting for password hashing.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect unsalted hashes but does not prevent their introduction.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC processes can include password-handling rules but do not guarantee salted hashes.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate salted hashing but do not prescribe the technical detail.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly forbid unsalted password hashes and require salting.

A.8.5 Secure authentication partial match
prevents

Secure authentication mandates salted, one-way hashes for credentials, directly preventing unsalted hashing.

References