# CVE-2026-33134: WeGIA has Authenticated Time-Based Blind SQL Injection in `restaurar_produto.php` via `id_produto` parameter

> Authenticated attackers can inject SQL via the id_produto parameter in restaurar_produto.php, leading to full database compromise in WeGIA.

- **Severity:** Critical 9.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Mar 2026
- **Updated:** 20 Mar 2026
- **Also known as:** GHSA-qg95-x997-66wq

## What is CVE-2026-33134?

CVE-2026-33134 is a critical SQL injection vulnerability in Wegia Wegia, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WeGIA is a web manager for charitable institutions. Versions 3.6.5 and below contain an authenticated SQL Injection vulnerability in the html/matPat/restaurar_produto.php endpoint. The vulnerability allows an authenticated attacker to inject arbitrary SQL commands via the id_produto GET parameter, leading to full database compromise. In the script /html/matPat/restaurar_produto.php, the application retrieves the id_produto parameter directly from the $_GET global array and interpolates it directly into two SQL query strings without any sanitization, type-casting (e.g., (int)), or using parameterized (prepare/execute) statements. This issue has been fixed in version 3.6.6.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-33134?

It affects 1 product.


Products: Wegia Wegia.

## How do I fix CVE-2026-33134?

No fix has been published for CVE-2026-33134 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-33134 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33134 exists.

## Other vulnerabilities in Wegia Wegia

- [CVE-2026-28409](https://insights.sbomify.com/CVE-2026-28409/): WeGIA Vulnerable to Remote Code Execution (RCE) via OS Command Injection (critical 10.0)
- [CVE-2025-58745](https://insights.sbomify.com/CVE-2025-58745/): WeGIA has a bypass for the fix for CVE-2025-22133 - Arbitrary File Upload leads to Remote Code Execution (RCE) (critical 10.0)
- [CVE-2025-58159](https://insights.sbomify.com/CVE-2025-58159/): WeGIA Authenticated Arbitrary File Upload Leading To Remote Code Execution (RCE) (critical 10.0)
- [CVE-2025-55169](https://insights.sbomify.com/CVE-2025-55169/): WeGIA Path Traversal at endpoint 'html/socio/sistema/download_remessa.php' via parameter 'file' (critical 10.0)
- [CVE-2025-53823](https://insights.sbomify.com/CVE-2025-53823/): WeGIA vulnerable to SQL Injection (Blind Time-Based) in `processa_deletar_socio.php` parameter `id_socio` (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33134 and fix it if it is affected.

What it is: CVE-2026-33134 is a critical SQL injection vulnerability in Wegia Wegia, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33134 exists.

Affected product: Wegia Wegia. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33134/ (Markdown: https://insights.sbomify.com/CVE-2026-33134/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33134
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33134
- OSV: https://osv.dev/vulnerability/CVE-2026-33134

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33134/
Summaries are generated and may contain mistakes; the official description above is the record.