# CVE-2026-54670: WeGIA: Unauthenticated Auth Bypass + Local File Inclusion

> Unauthenticated attackers can bypass authentication to access sensitive donation records and trigger financial workflows, or use path traversal to read local files.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 17 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-7p5g-g8xw-x47g

## What is CVE-2026-54670?

CVE-2026-54670 is a critical authentication bypass vulnerability in LabRedesCefetRJ WeGIA, published on 17 Sep 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. Prior to 3.8.5, the contribution request dispatcher in web/html/contribuicao/controller/control.php accepts attacker-controlled nomeClasse and metodo values without a complete controller and method allowlist, exempts sensitive ContribuicaoLogController operations from authentication, and constructs a controller include path without canonical directory containment. An unauthenticated remote attacker can invoke getContribuicoesLogJSON, sincronizarStatus, registrarFaturas, and other sensitive methods to disclose contribution and donation records or trigger financial workflow operations. A traversal-shaped nomeClasse value can also cause require_once to include an accessible PHP or configuration file outside the intended controller directory, exposing source code, credentials, or other sensitive local data. This issue is fixed in version 3.8.5.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-54670 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54670 is a critical authentication bypass vulnerability in LabRedesCefetRJ WeGIA, published on 17 Sep 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-54670 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-54670/ (Markdown: https://insights.sbomify.com/CVE-2026-54670/index.md)
```

## Sources

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

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