CVE-2026-61671: WeGIA unauthorized access to records via authentication bypass

CVE-2026-61671 · Severity: high · CVSS 8.1 · Published 2026-10-29

WeGIA is a web management system used by charitable institutions to manage beneficiary, internal staff, and volunteer records. Prior to version 3.8.7, any authenticated user can view, modify, or delete records belonging to other users—including sensitive personal data like CPF/RG, addresses, medical histories, and financial information—because the application fails to verify record ownership. Additionally, some record types lack CSRF protection, allowing attackers to perform these actions through malicious websites visited by authenticated victims.

Technologies: Wegia. Vendors: Wegia.

Quick answers

Is CVE-2026-61671 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-61671 being exploited in the wild.
How severe is CVE-2026-61671?
High severity, with a CVSS score of 8.1, published 29 October 2026.
Which products and versions are affected?
Wegia before 3.8.7.
Is there a fix for CVE-2026-61671?
Yes: fixed in 3.8.7. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-61671 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-61671?
Check whether you run Wegia at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Fixed in: 3.8.7

Technical details

The vulnerability stems from the `/controle/control.php` dispatcher using `extract($_REQUEST)` to populate class and method names without validating record ownership. The affected CRUD controllers (AtendidoControle, InternoControle, FuncionarioControle, VoluntarioControle) omit authorization checks on multiple methods, allowing any authenticated user to enumerate and modify records by controlling identifiers (id, idatendido, idInterno, id_funcionario). AtendidoControle and InternoControle additionally lack CSRF tokens on state-changing operations, enabling cross-site request forgery attacks by authenticated victims.

Affected products

  • WeGIA WeGIA before 3.8.7

Timeline

  • 2026-10-29: disclosed

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.