Unauthenticated SQL injection via unchecked billing identifier
Published Oct 14, 2026 · Updated Oct 14, 2026
SQL injection in WeGIA 3.8.5 and earlier allows remote attackers to read or modify database content via billing-update requests. In cadastro_cobranca.php, extract($_REQUEST) supplies codigo directly to an UPDATE statement's WHERE clause without validation or parameter binding. Network access suffices because the handler performs no session check; exposed data includes credential hashes and billing records.
Summary
What happened
SQL injection in WeGIA 3.8.5 and earlier allows remote attackers to read or modify database content via billing-update requests. In cadastro_cobranca.php, extract($_REQUEST) supplies codigo directly to an UPDATE statement's WHERE clause without validation or parameter binding. Network access suffices because the handler performs no session check; exposed data includes credential hashes and billing records.
The record
- CVE
- CVE-2026-55680
- Published
- Oct 14, 2026
- Updated
- Oct 14, 2026
- Vendor
- LabReDeS - Laboratório de Redes, Desenvolvimento e Segurança
- Product
- WeGIA
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 14, 2026CVE publishedPublication date reported by the CVE source.
- Oct 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.8.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
- Upstream HTTP proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started