SQL Injection in WeGIA (CVE-2025-62179)
Summary
SQL injection in WeGIA (CVE-2025-62179). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 3.5.1 or later.
Original description
The description as published by the source.
WeGIA is an open source Web Manager for Institutions with a focus on Portuguese language users. Prior to 3.5.1, a SQL Injection vulnerability was identified in the /html/funcionario/cadastro_funcionario_pessoa_existente.php endpoint, specifically in the cpf parameter. This vulnerability allows attackers to execute arbitrary SQL commands, compromising the confidentiality, integrity, and availability of the database. This vulnerability is fixed in 3.5.1.
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-2025-62179 has been found in WeGIA.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade WeGIA to 3.5.1 or later.
If unsure, ask your IT team or search "WeGIA CVE-2025-62179" on the vendor's site.
CVE-2025-62179 (WeGIA) — CWE-89 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Patched: 3.5.1 — apply immediately
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.
SQL injection (CWE-89) exists in WeGIA.
Check the vendor advisory for the affected versions of WeGIA.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to 3.5.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. 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
-
1Identify exposure identify
grep -r 'WeGIA' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
WeGIAを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade WeGIA to 3.5.1ステージング環境で 3.5.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- exploit security-advisories@github.com
- patch security-advisories@github.com