Categories
CVE-2026-55681 high CVSS 8.8

SQL Injection in WeGIA (CVE-2026-55681)

Summary

SQL injection in WeGIA (CVE-2026-55681). Successful exploitation can lead to full system takeover. Exploitable via GET /html/matPat/restaurar_produto_desocultar.php.

Original description

The description as published by the source.

WeGIA is a web manager for charitable institutions. Prior to 3.8.6, an authenticated user with access to the Material & Patrimônio module can submit id_produto to web/html/matPat/restaurar_produto_desocultar.php, where a second extract($_REQUEST) overwrites the value previously sanitized by intval(). The raw value is interpolated into UPDATE statements for the produto, isaida, and ientrada tables. An attacker can execute arbitrary SQL to extract sensitive database records or modify institutional and inventory data. This issue is fixed in version 3.8.6.

Source: NIST National Vulnerability Database NVD

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-55681 has been found in WeGIA.
Attackers can target a specific entry point like GET /html/matPat/restaurar_produto_desocultar.php over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "WeGIA CVE-2026-55681" on the vendor's site.

CVE-2026-55681 (WeGIA) — CWE-89 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /html/matPat/restaurar_produto_desocultar.php / id_produto / permissao / id_cargo
Affected: <= 3.8.5
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

SQL injection (CWE-89) exists in WeGIA. Attackers reach the vulnerable code path via GET /html/matPat/restaurar_produto_desocultar.php.

📍 Affected scope

Affected versions of WeGIA: <= 3.8.5. Attack surface: GET /html/matPat/restaurar_produto_desocultar.php / id_produto / permissao / id_cargo.

🔥 Severity

Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to the patched release per vendor advisory. (If a vulnerable version <= 3.8.5 is in production, plan an immediate maintenance window.)

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual GET /html/matPat/restaurar_produto_desocultar.php requests with malformed payloads or SQL meta-characters. Run grep -r 'WeGIA' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'WeGIA' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で WeGIA を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Match against affected range verify
    Confirm if version satisfies `<= 3.8.5`

    Step 1 で見つかったバージョンが影響範囲 <= 3.8.5 に該当するか照合。本番で稼働中ならインシデント扱い。

  3. 3
    Hunt for indicators of compromise detect
    grep 'GET /html/matPat/restaurar_produto_desocultar.php' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで GET /html/matPat/restaurar_produto_desocultar.php への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  4. 4
    Post-deployment verification verify
    Replay attack against GET /html/matPat/restaurar_produto_desocultar.php on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details