Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-23724: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in LabRedesCefetRJ WeGIA

0
Medium
VulnerabilityCVE-2026-23724cvecve-2026-23724cwe-79
Published: Fri Jan 16 2026 (01/16/2026, 19:37:06 UTC)
Source: CVE Database V5
Vendor/Project: LabRedesCefetRJ
Product: WeGIA

Description

CVE-2026-23724 is a medium severity stored Cross-Site Scripting (XSS) vulnerability in the WeGIA web management application for charitable institutions, specifically affecting versions prior to 3. 6. 2. The vulnerability exists in the html/atendido/cadastro_ocorrencia. php endpoint where user input is not properly sanitized before being rendered inside a dropdown selection, allowing malicious scripts to be stored and executed in users' browsers. Exploitation requires network access and low privileges but no user interaction, potentially leading to confidentiality breaches such as session hijacking or data exposure. The vulnerability has a CVSS score of 4. 3 and is fixed in version 3. 6. 2.

AI-Powered Analysis

AILast updated: 01/23/2026, 20:36:07 UTC

Technical Analysis

CVE-2026-23724 is a stored Cross-Site Scripting (XSS) vulnerability identified in the WeGIA web management system developed by LabRedesCefetRJ, targeting charitable institutions. The flaw resides in the html/atendido/cadastro_ocorrencia.php endpoint, where user-supplied data is incorporated into the “Atendido” selection dropdown without proper sanitization or encoding. This improper neutralization of input (CWE-79) allows attackers to inject malicious JavaScript code that is stored on the server and executed in the browsers of users who access the affected page. The vulnerability requires an attacker to have network access and low privileges (PR:L) but does not require user interaction (UI:N), making it easier to exploit in automated or targeted attacks. The impact primarily affects confidentiality, as attackers could steal session cookies or other sensitive information accessible via the browser context. The vulnerability does not affect integrity or availability directly. The issue was fixed in WeGIA version 3.6.2 by properly sanitizing user input before rendering it in the dropdown. No known exploits are currently reported in the wild, but the presence of stored XSS in a web management tool used by charitable organizations poses a risk of targeted attacks or phishing campaigns leveraging the trusted platform. The CVSS score of 4.3 reflects a medium severity, considering the ease of exploitation and limited impact scope.

Potential Impact

For European organizations using WeGIA, particularly those managing charitable or social service operations, this vulnerability could lead to unauthorized disclosure of sensitive information such as session tokens or personal data through malicious script execution in users' browsers. This could facilitate further attacks like account hijacking or phishing. While the vulnerability does not directly compromise system integrity or availability, the confidentiality breach can undermine trust in the platform and lead to reputational damage. Given the nature of WeGIA’s user base, exploitation could also impact vulnerable populations served by these institutions. The risk is heightened in environments where multiple users access the application and where security awareness may be limited. Additionally, the lack of required user interaction means that exploitation can occur silently, increasing the threat to European entities relying on this software.

Mitigation Recommendations

The primary mitigation is to upgrade all WeGIA instances to version 3.6.2 or later, where the vulnerability is patched. Organizations should also implement strict input validation and output encoding on all user-supplied data, especially in dropdowns and form fields, to prevent injection of malicious scripts. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers. Conduct regular security audits and penetration testing focusing on web application input handling. Monitor logs and user activity for unusual behavior related to the vulnerable endpoint. Educate users about the risks of XSS and encourage cautious handling of unexpected content. If immediate patching is not feasible, consider applying web application firewall (WAF) rules to detect and block suspicious payloads targeting the affected parameter. Finally, maintain an incident response plan to quickly address any exploitation attempts.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-01-15T15:45:01.955Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 696a96c8b22c7ad868e58b73

Added to database: 1/16/2026, 7:51:36 PM

Last enriched: 1/23/2026, 8:36:07 PM

Last updated: 2/7/2026, 12:15:35 PM

Views: 40

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats