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-23728: CWE-601: URL Redirection to Untrusted Site ('Open Redirect') in LabRedesCefetRJ WeGIA

0
Medium
VulnerabilityCVE-2026-23728cvecve-2026-23728cwe-601
Published: Fri Jan 16 2026 (01/16/2026, 19:46:07 UTC)
Source: CVE Database V5
Vendor/Project: LabRedesCefetRJ
Product: WeGIA

Description

CVE-2026-23728 is an Open Redirect vulnerability in the WeGIA web manager for charitable institutions, affecting versions prior to 3. 6. 2. The flaw exists in the /WeGIA/controle/control. php endpoint via the nextPage parameter when used with metodo=listarTodos and nomeClasse=DestinoControle, allowing attackers to redirect users to arbitrary external sites. This can facilitate phishing, credential theft, malware distribution, and social engineering by exploiting the trusted WeGIA domain. The vulnerability requires no authentication but does require user interaction to follow the malicious link. It has a CVSS score of 4. 8, indicating medium severity, and has no known exploits in the wild. The issue is fixed in version 3.

AI-Powered Analysis

AILast updated: 01/23/2026, 20:37:16 UTC

Technical Analysis

CVE-2026-23728 is an Open Redirect vulnerability classified under CWE-601, found in the WeGIA web management application developed by LabRedesCefetRJ, primarily used by charitable institutions. The vulnerability resides in the /WeGIA/controle/control.php endpoint, specifically in the nextPage parameter when combined with the parameters metodo=listarTodos and nomeClasse=DestinoControle. The application fails to properly validate or restrict the nextPage parameter, enabling an attacker to craft URLs that redirect users to arbitrary external websites. This lack of validation allows attackers to exploit the trusted WeGIA domain to conduct phishing attacks, steal credentials, distribute malware, or perform social engineering. The vulnerability does not require authentication but does require user interaction, such as clicking a malicious link. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:L), user interaction required (UI:A), and low impact on confidentiality, integrity, and availability. No known exploits are currently reported in the wild. The vulnerability is addressed in WeGIA version 3.6.2, where proper validation of the nextPage parameter has been implemented to prevent arbitrary redirection.

Potential Impact

For European organizations, especially charitable institutions using WeGIA versions prior to 3.6.2, this vulnerability poses a risk of phishing and social engineering attacks leveraging the trusted WeGIA domain. Attackers can redirect users to malicious sites to harvest credentials or distribute malware, potentially leading to data breaches or compromised systems. Although the direct impact on system integrity or availability is low, the indirect consequences through successful phishing or malware infections can be significant, including reputational damage and regulatory penalties under GDPR if personal data is compromised. The requirement for user interaction limits automated exploitation but does not eliminate risk, especially in environments where users may be less security-aware. The medium CVSS score reflects these factors. Organizations relying on WeGIA for managing charitable activities should consider the reputational and operational risks arising from exploitation of this vulnerability.

Mitigation Recommendations

European organizations should immediately upgrade WeGIA to version 3.6.2 or later to apply the official fix that validates the nextPage parameter and prevents open redirects. Until the upgrade is completed, organizations should implement web application firewall (WAF) rules to detect and block suspicious requests containing manipulated nextPage parameters. Security awareness training should emphasize caution when clicking links, especially those purporting to come from trusted internal applications. Additionally, organizations can implement URL filtering and email gateway protections to detect and quarantine phishing attempts exploiting this vulnerability. Monitoring web server logs for unusual redirect patterns can help identify exploitation attempts. Finally, organizations should review and restrict the use of the vulnerable endpoint where possible and consider additional input validation or URL sanitization at the application or proxy level as a temporary mitigation.

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.956Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 696a96c8b22c7ad868e58b5f

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

Last enriched: 1/23/2026, 8:37:16 PM

Last updated: 2/7/2026, 10:23:41 AM

Views: 12

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