# CVE-2026-61671: WeGIA: Systemic IDOR + Missing CSRF — extract($_REQUEST) in All Controle Classes


- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026

## What is CVE-2026-61671?

CVE-2026-61671 is a high-severity vulnerability in LabRedesCefetRJ WeGIA, published on 29 Oct 2026. 

### Official description

WeGIA is a web manager for charitable institutions. Prior to the advisory's stated patched version 3.8.7, the `/controle/control.php` dispatch endpoint accepts attacker-controlled `nomeClasse`, `metodo`, and record identifier parameters through `extract($_REQUEST)`, including id, `idatendido`, `idInterno`, and `id_funcionario`, while the affected Controle CRUD methods do not verify record ownership. Any authenticated user can view, modify, or delete another user's records, exposing CPF, RG, addresses, medical records, financial data, and employee records. `AtendidoControle` lacks ownership checks on alterar, excluir, `listarUm`, `alterarInfPessoal`, `alterarDocumentacao`, `alterarImagem`, `alterarEndereco`, and `alterarStatus`; `InternoControle` lacks them on incluir, alterar, excluir, `listarUm`, `listarTodos`, and `listarCpf`. `FuncionarioControle` lacks ownership checks on `alterarInfPessoal`, `alterarEndereco`, `alterarDocumentacao`, `alterarImagem`, `alterarCargaHoraria`, and excluir; `VoluntarioControle` lacks them on `alterarInfPessoal`, `alterarEndereco`, `alterarDetalhes`, `alterarImagem`, and excluir. `AtendidoControle` and `InternoControle` additionally lack CSRF validation, allowing a malicious page visited by an authenticated victim to perform state-changing operations using the victim's session. `FuncionarioControle` and `VoluntarioControle` have per-method CSRF checks, but those checks do not prevent the object-authorization bypass. The advisory identifies version 3.8.7 as patched.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2026-61671 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-61671 is a high-severity vulnerability in LabRedesCefetRJ WeGIA, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-61671 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-61671/ (Markdown: https://insights.sbomify.com/CVE-2026-61671/index.md)
```

## Sources

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

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