Goal Reached Thanks to every supporter β€” we hit 100%!

Goal: 1000 CNY Β· Raised: 1000 CNY

100.0%

CVE-2026-23722 β€” AI Deep Analysis Summary

CVSS 9.1 Β· Critical

Q1What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: Reflected XSS in WeGIA. πŸ“‰ **Consequences**: Attackers inject malicious scripts via the `id_memorando` GET parameter. Victims execute code in their browser, leading to session hijacking or data theft.

Q2Root Cause? (CWE/Flaw)

πŸ›‘οΈ **Root Cause**: CWE-79 (Improper Neutralization of Input). πŸ› **Flaw**: The file `html/memorando/insere_despacho.php` fails to sanitize/encode user input from the `id_memorando` parameter before rendering it in HTML.

Q3Who is affected? (Versions/Components)

🏒 **Vendor**: LabRedesCefetRJ (Nilson Lazarin). πŸ“¦ **Product**: WeGIA (Welfare Institution Network Manager). ⚠️ **Affected**: Versions **prior to 3.6.2**.

Q4What can hackers do? (Privileges/Data)

πŸ’» **Privileges**: No authentication required (PR:N). πŸ•΅οΈ **Data**: High impact on Confidentiality & Integrity (C:H, I:H). Hackers can steal cookies, redirect users, or deface pages via reflected script execution.

Q5Is exploitation threshold high? (Auth/Config)

πŸ”“ **Threshold**: LOW. 🌐 **Config**: Network Accessible (AV:N). No Privileges Required (PR:N). No User Interaction Required (UI:N). It is a trivial, remote exploit.

Q6Is there a public Exp? (PoC/Wild Exploitation)

πŸ“œ **Public Exp**: No specific PoC code provided in data. πŸ” **Status**: Advisory confirmed via GitHub Security Advisory (GHSA-g7hh-6qj7-mcqf). Exploitation logic is straightforward given the reflection nature.

Q7How to self-check? (Features/Scanning)

πŸ” **Self-Check**: Scan for `id_memorando` parameter in `insere_despacho.php`. πŸ§ͺ **Test**: Inject `<script>alert(1)</script>` into the GET request. If reflected/executed, the system is vulnerable.

Q8Is it fixed officially? (Patch/Mitigation)

πŸ”§ **Fix**: Upgrade to **WeGIA version 3.6.2** or later. πŸ“₯ **Source**: Official GitHub repository advisory confirms the patch exists in the newer release.

Q9What if no patch? (Workaround)

🚧 **Workaround**: If patching is delayed, implement strict input validation on the server side. πŸ›‘οΈ **Mitigation**: Encode all output related to `id_memorando` using HTML entity encoding before rendering.

Q10Is it urgent? (Priority Suggestion)

πŸ”₯ **Urgency**: HIGH. 🚨 **Priority**: CVSS 3.1 Score indicates Critical impact (C:H, I:H). Immediate patching is recommended due to zero-auth requirement and high severity.