WeGIA 3.8.6 Patch Fixes Critical Unauthenticated SQL Injection Flaw
LabRedesCefetRJ released WeGIA version 3.8.6 to address a critical SQL injection vulnerability that allows attackers to manipulate billing records and user credentials without authentication.

Key points
- CVE-2026-55680 is rated 9.8 Critical on the CVSS scale by the National Vulnerability Database.
- The flaw allows unauthenticated attackers to execute arbitrary SQL via the cadastro_cobranca.php script.
- Version 3.8.6 fixes the issue by validating input and preventing direct query manipulation.
LabRedesCefetRJ has released version 3.8.6 of the WeGIA web management system to fix a critical security vulnerability. The update addresses CVE-2026-55680, a severe flaw that permits unauthenticated attackers to execute arbitrary SQL commands against the application’s database without needing valid login credentials.
At a glance
- CVE
- CVE-2026-55680
- Product
- LabRedesCefetRJ WeGIA
- CVSS
- 9.8 Critical
- Weakness
- SQL injection
- Exploited
- No known exploitation
The National Vulnerability Database rates this issue as Critical with a CVSS score of 9.8. The vulnerability exists in the cadastro_cobranca.php script, which handles billing data entry. Attackers can send malicious POST requests to this endpoint, injecting SQL expressions through the codigo parameter. This allows for direct manipulation of the underlying database structure and content.
Technical Details of the Vulnerability
The root cause lies in how the application processes user input. The script uses the extract($_REQUEST) function to import variables directly into the local symbol table. This mechanism passes the codigo parameter value into an UPDATE statement’s WHERE clause without any validation or parameter binding. Because the input is not sanitized, attackers can inject quoted SQL expressions that bypass MariaDB’s type conversion for VARCHAR columns.
As described in the NVD record, this lack of validation enables arbitrary SQL execution. An attacker can read or modify sensitive database content, including user credential hashes and billing records stored in the cobrancas table. The flaw affects all versions of WeGIA prior to 3.8.6, leaving any unpatched installation vulnerable to remote exploitation by anyone with network access.
This incident mirrors broader trends in content management systems where improper input handling leads to severe breaches. As Threat Times reported on 2026-10-14, e107 CMS version 2.3.7 also fixed a critical unauthenticated SQL injection in its Alt Auth plugin, highlighting the persistent risk of similar coding errors in web applications.
Affected Systems and Scope
The vulnerability impacts WeGIA, a web manager designed specifically for charitable institutions. Organizations using this software to manage donations, billing, and member data are at risk. Since the attack does not require authentication, any publicly accessible instance of WeGIA running a version older than 3.8.6 is exposed.
The ability to access the cobrancas table is particularly dangerous for non-profit entities. Billing records often contain sensitive financial information and donor details. Compromise of this data could lead to significant privacy violations and financial fraud. The critical severity rating reflects the ease of exploitation and the high impact on confidentiality, integrity, and availability.
What should you do?
Administrators running WeGIA should immediately verify their current version. If the system is below version 3.8.6, they must apply the latest update to patch the SQL injection vulnerability. Delaying the update leaves the database open to unauthenticated attacks that can exfiltrate or alter critical organizational data.
What to do and how to stay safe: WeGIA
- Check the installed version of WeGIA and upgrade to 3.8.6 or later to apply the security fix.
- Review database logs for unusual UPDATE statements or queries involving the codigo parameter.
- Restrict access to the cadastro_cobranca.php endpoint using web application firewalls until patched.
- Monitor for unauthorized changes to user credential hashes and billing records in the cobrancas table.
Step-by-step guide: Risk-Based Vulnerability Management: Prioritize Fixes by Actual Danger
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is the CVSS score for CVE-2026-55680?
The National Vulnerability Database rates CVE-2026-55680 as Critical with a CVSS score of 9.8.
Which versions of WeGIA are affected by this vulnerability?
All versions of WeGIA prior to 3.8.6 are affected by this unauthenticated SQL injection flaw.
Can attackers exploit this vulnerability without logging in?
Yes, the vulnerability allows unauthenticated attackers to execute SQL commands via POST requests.


