# CVE-2026-76633: WeGIA < 3.9.2 Authorization Bypass Password Change via alterarSenha

> Authenticated users can bypass password verification to permanently take over accounts by manipulating routing parameters in WeGIA.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Aug 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-8248-cv95-x854, GHSA-gfcx-7973-hjmp

## What is CVE-2026-76633?

CVE-2026-76633 is a high-severity authentication bypass vulnerability in LabRedesCefetRJ WeGIA, published on 20 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

WeGIA before 3.9.2 contains an authorization bypass vulnerability in the password change flow that allows any authenticated user to change their account password without providing existing credentials by exploiting the unconditional exclusion of the alterarSenha method from permission checks in controle/control.php. Attackers can manipulate the redir parameter to point to alterar_senha.php, routing through verificarSenhaConfig() instead of verificarSenha() to bypass current password verification and convert temporary session access into permanent account takeover.

Weakness: CWE-862 (Missing Authorization), CWE-620 (Unverified Password Change)

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


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

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

## Is CVE-2026-76633 being exploited?

There is no known exploitation of CVE-2026-76633 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-76633 is a high-severity authentication bypass vulnerability in LabRedesCefetRJ WeGIA, published on 20 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-76633 in the wild and no public exploit code.

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-76633/ (Markdown: https://insights.sbomify.com/CVE-2026-76633/index.md)
```

## Sources

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

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