Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-33991: CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in LabRedesCefetRJ WeGIA

0
High
VulnerabilityCVE-2026-33991cvecve-2026-33991cwe-89
Published: Fri Mar 27 2026 (03/27/2026, 22:10:51 UTC)
Source: CVE Database V5
Vendor/Project: LabRedesCefetRJ
Product: WeGIA

Description

WeGIA is a web manager for charitable institutions. Prior to version 3.6.7, the file `html/socio/sistema/deletar_tag.php` uses `extract($_REQUEST)` on line 14 and directly concatenates the `$id_tag` variable into SQL queries on lines 16-17 without prepared statements or sanitization. Version 3.6.7 patches the vulnerability.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/27/2026, 22:36:06 UTC

Technical Analysis

CVE-2026-33991 is an SQL Injection vulnerability identified in the WeGIA web management system developed by LabRedesCefetRJ, specifically affecting versions prior to 3.6.7. The vulnerability is located in the file `html/socio/sistema/deletar_tag.php`, where the PHP function extract($_REQUEST) is used on line 14 to import request variables into the local symbol table. Subsequently, the variable `$id_tag` derived from user input is directly concatenated into SQL queries on lines 16 and 17 without any sanitization or use of prepared statements. This improper neutralization of special elements in SQL commands (CWE-89) allows an attacker with low privileges to inject malicious SQL code remotely, potentially leading to unauthorized data access, modification, or deletion. The vulnerability does not require user interaction and can be exploited over the network, increasing its risk profile. The vendor addressed this issue in version 3.6.7 by presumably implementing proper input validation and prepared statements to prevent injection. The CVSS v3.1 base score is 8.8, reflecting high impact on confidentiality, integrity, and availability, with low attack complexity and no user interaction required. No known exploits have been reported in the wild as of the publication date. This vulnerability highlights the risks of unsafe PHP coding practices and the importance of secure input handling in web applications managing sensitive data.

Potential Impact

The exploitation of CVE-2026-33991 can have severe consequences for organizations using vulnerable versions of WeGIA. Attackers can execute arbitrary SQL commands, leading to unauthorized disclosure of sensitive data such as donor information, financial records, or personal details of beneficiaries. Data integrity can be compromised by unauthorized modification or deletion of records, potentially disrupting charitable operations and eroding trust. Availability may also be affected if attackers delete critical data or cause database corruption, resulting in service outages. Given that WeGIA is used by charitable institutions, such disruptions could impact critical social services and fundraising activities. The ease of exploitation and network accessibility make this vulnerability attractive to attackers, including opportunistic cybercriminals and potentially nation-state actors targeting social sector organizations. The lack of known exploits in the wild currently reduces immediate risk but does not eliminate the threat, especially if attackers develop proof-of-concept exploits. Organizations failing to patch may face data breaches, regulatory penalties, reputational damage, and operational interruptions.

Mitigation Recommendations

Organizations using WeGIA should immediately upgrade to version 3.6.7 or later, where the vulnerability is patched. If upgrading is not immediately feasible, implement the following mitigations: 1) Apply web application firewall (WAF) rules to detect and block SQL injection patterns targeting the vulnerable endpoint `html/socio/sistema/deletar_tag.php`. 2) Restrict database user permissions to the minimum necessary to limit the impact of injection attacks. 3) Conduct code audits to identify and refactor any other instances of unsafe input handling, replacing extract($_REQUEST) with explicit input validation and using parameterized queries or prepared statements. 4) Monitor application logs for suspicious activity indicative of injection attempts. 5) Educate developers on secure coding practices to prevent similar vulnerabilities. 6) Employ runtime application self-protection (RASP) tools if available to detect and block injection attacks in real time. These measures, combined with patching, will significantly reduce the risk of exploitation.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-03-24T22:20:06.211Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69c702cd2b68dbd88e2edf8b

Added to database: 3/27/2026, 10:21:01 PM

Last enriched: 3/27/2026, 10:36:06 PM

Last updated: 3/28/2026, 12:03:27 AM

Views: 7

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses