# CVE-2026-45027: WeGIA: Use of Weak Password Hashing Algorithm (SHA-256, no salt) in html/login.php

> Attackers can recover user passwords via rainbow tables due to unsalted SHA-256 hashing, compromising accounts in WeGIA.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 May 2026
- **Updated:** 27 May 2026
- **Also known as:** GHSA-hcgv-vmq6-j6qg

## What is CVE-2026-45027?

CVE-2026-45027 is a medium-severity vulnerability in LabRedesCefetRJ WeGIA, published on 27 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-916 (Use of Password Hash With Insufficient Computational Effort), CWE-759 (Use of a One-Way Hash without a Salt)

## Which versions are affected by CVE-2026-45027?


## How do I fix CVE-2026-45027?

No fix has been published for CVE-2026-45027 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-45027 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45027 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-45027 and fix it if it is affected.

What it is: CVE-2026-45027 is a medium-severity vulnerability in LabRedesCefetRJ WeGIA, published on 27 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45027 exists.

Affected product: LabRedesCefetRJ WeGIA. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-45027/ (Markdown: https://insights.sbomify.com/CVE-2026-45027/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-45027
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-45027
- OSV: https://osv.dev/vulnerability/CVE-2026-45027

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-45027/
Summaries are generated and may contain mistakes; the official description above is the record.