{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45027 exists.","fix":"No fix has been published for CVE-2026-45027 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-45027 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45027 exists.\n\nAffected product: LabRedesCefetRJ WeGIA. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-45027/ (Markdown: https://insights.sbomify.com/CVE-2026-45027/index.md)","id":"CVE-2026-45027","markdown":"https://insights.sbomify.com/CVE-2026-45027/index.md","name":"CVE-2026-45027","record":{"aliases":["GHSA-hcgv-vmq6-j6qg"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Charitable institution manager","requires_auth":"none","summary":"Attackers can recover user passwords via rainbow tables due to unsalted SHA-256 hashing, compromising accounts in WeGIA.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-916","name":"Use of Password Hash With Insufficient Computational Effort"},{"id":"CWE-759","name":"Use of a One-Way Hash without a Salt"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"WeGIA: Use of Weak Password Hashing Algorithm (SHA-256, no salt) in html/login.php","id":"CVE-2026-45027","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Astro: Server island encrypted parameters vulnerable to cross-component replay","id":"CVE-2026-45028"},"packages":[],"prev":{"headline":"WeGIA: Stored XSS in html/atendido/processo_aceitacao.php","id":"CVE-2026-45026"},"products":["WeGIA"],"published":"2026-05-27","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-27","vendors":["LabRedesCefetRJ"]},"summary":"Attackers can recover user passwords via rainbow tables due to unsalted SHA-256 hashing, compromising accounts in WeGIA.","url":"https://insights.sbomify.com/CVE-2026-45027/"}