Cross-Site Scripting (XSS) in WeGIA (CVE-2025-62178)
Summary
Cross-site scripting in WeGIA (CVE-2025-62178). Risk of unauthorized operations or information disclosure. 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 Reflected Cross-Site Scripting (XSS) vulnerability was identified in the /html/atendido/cadastro_atendido_parentesco_pessoa_nova.php endpoint of the WeGIA application. This vulnerability allows attackers to inject malicious scripts in the idatendido parameter. 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-62178 has been found in WeGIA.
Risk of unauthorized operations or information disclosure. CVSS score: 3.5/10.
What to do: upgrade WeGIA to 3.5.1 or later.
If unsure, ask your IT team or search "WeGIA CVE-2025-62178" on the vendor's site.
CVE-2025-62178 (WeGIA) — CWE-79 / CVSS v3 3.5
Attack vector: remote (network-reachable)
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.
Cross-site scripting (XSS) (CWE-79) exists in WeGIA.
Check the vendor advisory for the affected versions of WeGIA.
Severity: Low (CVSS 3.5/10). Risk of unauthorized operations or information disclosure.
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 でアラート再発が無いか継続監視。