VulnerabilityPublished 20 Mar 2026

CVE-2026-33134: LabRedesCefetRJ WeGIA · SQL Injection

Affects LabRedesCefetRJ WeGIASource CVE Database V5

Compare

Not known to be exploited · CVSS 9.3 Critical : upgrade to 3.6.6 as a priority.

Data as of 31 Oct 2026, 20:20 UTC

CVSS 3.1 base score

9.3Critical

How severe the flaw is on the 0–10 CVSS scale.

Contested

Critical score, yet low EPSS after six months

EPSS: 0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.6.6

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 31 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade WeGIA and labredescefetrj/WeGIA to 3.6.6.

Affected software

Product	Affected	Fixed in
LabRedesCefetRJWeGIA	Affected <3.6.6	Fixed in 3.6.6
GitHublabredescefetrj/WeGIA`pkg:github/labredescefetrj/WeGIA`Other threats	Affected <3.6.6	Fixed in 3.6.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should immediately upgrade WeGIA to version 3.6.6 or later, where the vulnerability has been fixed. Until the upgrade is applied, restrict access to the vulnerable endpoint (html/matPat/restaurar_produto.php) using network-level controls such as firewalls or VPNs to limit exposure. Implement strict input validation and enforce type casting on all user-supplied parameters, particularly id_produto, to ensure only valid integer values are accepted. Employ parameterized SQL queries (prepared statements) throughout the application to prevent SQL injection. Conduct thorough code reviews and security testing to identify and remediate similar injection flaws elsewhere in the application. Monitor logs for suspicious activity indicative of SQL injection attempts or unauthorized access. Enforce strong authentication and access controls to reduce the risk of credential compromise. Finally, educate developers on secure coding practices to prevent recurrence of such vulnerabilities.

Description

CVE-2026-33134 is a critical SQL Injection vulnerability in WeGIA, a web management system for charitable institutions, affecting versions 3.6.5 and below. The flaw exists in the html/matPat/restaurar_produto.php endpoint, where the id_produto GET parameter is unsafely interpolated into SQL queries without sanitization or parameterization. An authenticated attacker can exploit this to execute arbitrary SQL commands, potentially leading to full database compromise. The vulnerability has been fixed in version 3.6.6. Exploitation requires authentication but no user interaction, and the vulnerability allows high confidentiality impact with limited integrity impact and no availability impact.

Impact

The primary impact of CVE-2026-33134 is the potential full compromise of the database backend of WeGIA installations running vulnerable versions. This can lead to unauthorized disclosure of sensitive information managed by charitable institutions, including donor data, financial records, and operational details. Attackers could also manipulate or delete data, undermining data integrity and trustworthiness. Although availability is not directly affected, the loss of data confidentiality and integrity can severely disrupt organizational operations and damage reputations. Given that WeGIA is used by charitable organizations, the exposure of donor and beneficiary information could have legal and compliance ramifications, including violations of data protection regulations. The requirement for authentication limits exploitation to insiders or attackers who have obtained valid credentials, but the lack of user interaction and the network accessibility of the vulnerable endpoint increase the risk. Organizations worldwide using WeGIA versions below 3.6.6 face significant risk of data breaches and operational disruption if this vulnerability is exploited.

CWE-89Improper Neutralization of Special Elements used in an SQL Command (SQL Injection) (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #2OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Parameterization
If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.
Architecture and Design · Operation · Environment Hardening
Run your code using the lowest privileges that are required to accomplish the necessary tasks. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment.
OWASP Cheat Sheets
Query Parameterization (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
XML Security (opens in a new tab)
XML External Entity Prevention (opens in a new tab)
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.4 (opens in a new tab)
V5.3.5 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
Command Line Execution through SQL Injection (opens in a new tab)
Object Relational Mapping Injection (opens in a new tab)
SQL Injection through SOAP Parameter Tampering (opens in a new tab)
Expanding Control over the Operating System from the Database (opens in a new tab)
SQL Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Mar 2026, 19:42 UTC

WeaknessesCWE-89

Technical details

References

Community reviews

Related threats