CVE-2026-33991
SQL Injection in WeGIA's deletar_tag.php Allows Data Manipulation
Publication date: 2026-03-27
Last updated on: 2026-03-31
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wegia | wegia | to 3.6.7 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability exists in WeGIA, a web manager for charitable institutions, in versions prior to 3.6.7. Specifically, the file `html/socio/sistema/deletar_tag.php` uses the PHP function `extract($_REQUEST)` which imports user-supplied request variables into the local symbol table. Then, the variable `$id_tag` is directly concatenated into SQL queries without any sanitization or use of prepared statements. This creates a risk of SQL injection attacks.
How can this vulnerability impact me? :
This vulnerability can have severe impacts because it allows an attacker to perform SQL injection. The CVSS score of 8.8 indicates high severity with potential for high confidentiality, integrity, and availability impacts. An attacker could manipulate or delete data, gain unauthorized access, or disrupt the service of the WeGIA application.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, upgrade WeGIA to version 3.6.7 or later, as this version patches the issue.
Avoid using the vulnerable file `html/socio/sistema/deletar_tag.php` in versions prior to 3.6.7, since it uses unsafe practices such as `extract($_REQUEST)` and direct concatenation of user input into SQL queries without sanitization or prepared statements.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability in WeGIA prior to version 3.6.7 involves SQL injection due to unsanitized input being concatenated directly into SQL queries. This can lead to unauthorized access, data modification, or data loss.
Such security weaknesses can impact compliance with common standards and regulations like GDPR and HIPAA, which require protection of sensitive data and prevention of unauthorized access or data breaches.
Specifically, exploitation of this vulnerability could result in confidentiality, integrity, and availability violations of protected data, potentially leading to non-compliance with these regulations.