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-28411: CWE-288: Authentication Bypass Using an Alternate Path or Channel in LabRedesCefetRJ WeGIA

0
Critical
VulnerabilityCVE-2026-28411cvecve-2026-28411cwe-288cwe-473
Published: Fri Feb 27 2026 (02/27/2026, 21:52:05 UTC)
Source: CVE Database V5
Vendor/Project: LabRedesCefetRJ
Product: WeGIA

Description

WeGIA is a web manager for charitable institutions. Prior to version 3.6.5, an unsafe use of the `extract()` function on the `$_REQUEST` superglobal allows an unauthenticated attacker to overwrite local variables in multiple PHP scripts. This vulnerability can be leveraged to completely bypass authentication checks, allowing unauthorized access to administrative and protected areas of the WeGIA application. Version 3.6.5 fixes the issue.

AI-Powered Analysis

AILast updated: 02/27/2026, 22:12:00 UTC

Technical Analysis

CVE-2026-28411 is a critical security vulnerability identified in the WeGIA web management software developed by LabRedesCefetRJ. The vulnerability stems from the unsafe use of PHP's extract() function on the $_REQUEST superglobal array in multiple PHP scripts prior to version 3.6.5. The extract() function imports variables from an array into the local symbol table, and when used on $_REQUEST, it allows an attacker to overwrite local variables by injecting parameters via GET, POST, or COOKIE data. This variable overwriting can subvert authentication logic by altering variables that control access checks, effectively bypassing authentication mechanisms without any credentials or user interaction. As a result, an unauthenticated attacker can gain unauthorized administrative access to the WeGIA application, compromising sensitive data and control functions. The vulnerability is classified under CWE-288 (Authentication Bypass Using an Alternate Path or Channel) and CWE-473 (Use of Function with Inconsistent Implementations), highlighting the root cause as insecure coding practices. The CVSS v3.1 base score is 9.8, reflecting the ease of exploitation over the network, no required privileges or user interaction, and full impact on confidentiality, integrity, and availability. Although no exploits have been observed in the wild, the critical nature of the flaw demands immediate attention. The vendor fixed the issue in version 3.6.5 by presumably removing or securing the use of extract() on untrusted input. Organizations running affected versions should prioritize patching to prevent unauthorized access and potential data breaches.

Potential Impact

The impact of CVE-2026-28411 is severe for organizations using WeGIA to manage charitable institutions. Successful exploitation allows attackers to bypass authentication controls entirely, granting unauthorized access to administrative and protected areas. This can lead to full compromise of the application, including unauthorized data disclosure, modification, or deletion of sensitive information related to charitable operations. Attackers could manipulate donation records, user accounts, or institutional data, potentially causing financial loss, reputational damage, and legal liabilities. The vulnerability also threatens the availability of the service if attackers disrupt or alter critical functions. Given the critical CVSS score and the lack of required privileges or user interaction, the risk of automated or mass exploitation is high once exploits become available. This could affect numerous organizations globally that rely on WeGIA for their web management needs, especially those handling sensitive donor or beneficiary information.

Mitigation Recommendations

To mitigate CVE-2026-28411, organizations should immediately upgrade WeGIA to version 3.6.5 or later, where the vulnerability has been addressed. If upgrading is not immediately feasible, apply temporary mitigations such as disabling or restricting access to vulnerable PHP scripts, especially those handling authentication, from untrusted networks. Review and sanitize all user input rigorously to prevent variable overwriting, avoiding the use of extract() on superglobals like $_REQUEST. Implement web application firewalls (WAFs) with rules to detect and block suspicious parameter injection attempts targeting variable overwriting. Conduct thorough code audits to identify and remediate similar unsafe coding patterns. Additionally, enforce strict access controls and monitor logs for unusual authentication bypass attempts. Educate developers on secure coding practices to prevent recurrence of such vulnerabilities.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-02-27T15:33:57.289Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69a212fb32ffcdb8a2777760

Added to database: 2/27/2026, 9:56:11 PM

Last enriched: 2/27/2026, 10:12:00 PM

Last updated: 2/28/2026, 12:00:15 AM

Views: 4

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

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses