Cross-Site Scripting (XSS) in WeGIA (CVE-2026-45025)
Summary
Cross-site scripting in WeGIA (CVE-2026-45025). Confidential information can be exposed externally. Mitigation: upgrade to 3.7.3 or later.
Original description
The description as published by the source.
WeGIA is a web manager for charitable institutions. In versions prior to 3.7.3, a Stored Cross-Site Scripting (XSS) vulnerability allows an authenticated user to inject malicious JavaScript into the "Etapas de um Processo" (html/atendido/etapa_processo.php) page, which is executed when user access the the page, enabling session hijacking and account takeover. This vulnerability is fixed in 3.7.3.
Source: NIST National Vulnerability Database NVD GitHub Advisory
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-45025 has been found in WeGIA.
Confidential information can be exposed externally. CVSS score: 6.8/10.
What to do: upgrade WeGIA to 3.7.3 or later.
If unsure, ask your IT team or search "WeGIA CVE-2026-45025" on the vendor's site.
CVE-2026-45025 (WeGIA) — CWE-79 / CVSS v3 6.8
Attack vector: remote (network-reachable) / no user interaction
Patched: 3.7.3 — 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: Medium (CVSS 6.8/10). Confidential information can be exposed externally.
Update to 3.7.3.
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.7.3ステージング環境で 3.7.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov