Password cracking via predictable person-ID salts
Published Apr 4, 2023 · Updated Feb 13, 2025
Insufficiently random password salting in ChurchCRM 4.5.3 allows attackers to crack stored password hashes through offline attacks. The User::getPasswordHash method concatenates each password with the integer person ID and applies raw SHA-256, making the salt predictable rather than randomly generated. Exploitation requires access to stored hashes; recovered passwords can enable unauthorized account access and disclosure of account-accessible data.
Summary
What happened
Insufficiently random password salting in ChurchCRM 4.5.3 allows attackers to crack stored password hashes through offline attacks. The User::getPasswordHash method concatenates each password with the integer person ID and applies raw SHA-256, making the salt predictable rather than randomly generated. Exploitation requires access to stored hashes; recovered passwords can enable unauthorized account access and disclosure of account-accessible data.
The record
- CVE
- CVE-2023-26855
- Published
- Apr 4, 2023
- Updated
- Feb 13, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-330, T1110.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 4, 2023CVE publishedPublication date reported by the CVE source.
- Feb 13, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo