CVE-2026-45027: CWE-759: Use of a One-Way Hash without a Salt in LabRedesCefetRJ WeGIA
WeGIA is a web manager for charitable institutions. In versions prior to 3.7.3, when a user logs in, html/login.php hashes the submitted password using PHP's hash() function with the SHA-256 algorithm and no salt before comparing it to the stored value. The password change flow in controle/FuncionarioControle.php follows the same pattern. SHA-256 is a general-purpose cryptographic hash built for speed, not password storage. Without a salt, identical passwords produce identical digests, making the entire hash database vulnerable to a single precomputed rainbow table lookup. This vulnerability is fixed in 3.7.3.
AI Analysis
Technical Summary
The vulnerability in WeGIA (CVE-2026-45027) arises from the use of PHP's hash() function with SHA-256 without a salt to hash user passwords during login and password change processes. SHA-256 is a fast, general-purpose hash function not designed for password storage, and the absence of a salt means that identical passwords yield identical hashes. This weakness enables attackers to use precomputed rainbow tables to reverse hashes and potentially recover user passwords. The issue affects all versions prior to 3.7.3 and is fixed in version 3.7.3.
Potential Impact
The vulnerability exposes password hashes to rainbow table attacks, potentially allowing attackers to recover user passwords if they obtain the hash database. This compromises user credential confidentiality but does not affect integrity or availability. There are no known exploits in the wild at this time.
Mitigation Recommendations
Upgrade WeGIA to version 3.7.3 or later, where the password hashing mechanism has been fixed to include salting or a more secure password hashing approach. Since no official patch link or advisory is provided, verify the upgrade availability with the vendor. Patch status is not yet confirmed beyond the stated fixed version; check the vendor advisory for current remediation guidance.
CVE-2026-45027: CWE-759: Use of a One-Way Hash without a Salt in LabRedesCefetRJ WeGIA
Description
WeGIA is a web manager for charitable institutions. In versions prior to 3.7.3, when a user logs in, html/login.php hashes the submitted password using PHP's hash() function with the SHA-256 algorithm and no salt before comparing it to the stored value. The password change flow in controle/FuncionarioControle.php follows the same pattern. SHA-256 is a general-purpose cryptographic hash built for speed, not password storage. Without a salt, identical passwords produce identical digests, making the entire hash database vulnerable to a single precomputed rainbow table lookup. This vulnerability is fixed in 3.7.3.
CVSS v3.1
Score 5.9medium
Affected software
pkg:github/labredescefetrj/WeGIARun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in WeGIA (CVE-2026-45027) arises from the use of PHP's hash() function with SHA-256 without a salt to hash user passwords during login and password change processes. SHA-256 is a fast, general-purpose hash function not designed for password storage, and the absence of a salt means that identical passwords yield identical hashes. This weakness enables attackers to use precomputed rainbow tables to reverse hashes and potentially recover user passwords. The issue affects all versions prior to 3.7.3 and is fixed in version 3.7.3.
Potential Impact
The vulnerability exposes password hashes to rainbow table attacks, potentially allowing attackers to recover user passwords if they obtain the hash database. This compromises user credential confidentiality but does not affect integrity or availability. There are no known exploits in the wild at this time.
Mitigation Recommendations
Upgrade WeGIA to version 3.7.3 or later, where the password hashing mechanism has been fixed to include salting or a more secure password hashing approach. Since no official patch link or advisory is provided, verify the upgrade availability with the vendor. Patch status is not yet confirmed beyond the stated fixed version; check the vendor advisory for current remediation guidance.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-08T16:58:28.896Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a171ce8e29bf47b50d1ded4
Added to database: 05/27/2026, 16:33:44 UTC
Last enriched: 05/27/2026, 16:49:11 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 103
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.