CVE-2026-23729VulnerabilityPublished 16 Jan 2026

CVE-2026-23729: LabRedesCefetRJ WeGIA · Open Redirect

Affects LabRedesCefetRJ WeGIASource CVE Database V5

Not known to be exploited · CVSS 4.8 Medium : upgrade to 3.6.2 when convenient.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 4.0 base score

4.8Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.6.2

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: Active
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: Low
Subsequent system integrity: Low
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: Active: Successful exploitation of this vulnerability requires a targeted user to perform specific, conscious interactions with the vulnerable system and the attacker’s payload, or the user’s interactions would actively subvert protection mechanisms which would lead to exploitation of the vulnerability.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Subsequent System.
Subsequent system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Subsequent System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade WeGIA and labredescefetrj/WeGIA to 3.6.2.

Affected software

Product	Affected	Fixed in
LabRedesCefetRJWeGIA	Affected <3.6.2	Fixed in 3.6.2
GitHublabredescefetrj/WeGIA`pkg:github/labredescefetrj/WeGIA`Other threats	Affected <3.6.2	Fixed in 3.6.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations using WeGIA should immediately upgrade to version 3.6.2 or later where the vulnerability is patched. Until the upgrade is applied, organizations should implement strict URL filtering and monitoring to detect and block suspicious redirects originating from the WeGIA domain. User education campaigns should be conducted to raise awareness about phishing risks and the dangers of clicking on unexpected links, even if they appear to come from trusted sources. Web application firewalls (WAFs) can be configured to detect and block requests with suspicious nextPage parameter values. Additionally, organizations should audit their WeGIA deployments to identify any customizations that might affect the patching process and ensure that all instances are updated. Logging and monitoring for unusual redirect patterns can help detect exploitation attempts early. Finally, consider implementing Content Security Policy (CSP) headers to restrict the domains to which users can be redirected.

Description

CVE-2026-23729 is an Open Redirect vulnerability in the WeGIA web management application used by charitable institutions. The flaw exists in versions prior to 3.6.2 within the /WeGIA/controle/control.php endpoint, specifically via the nextPage parameter when combined with certain query parameters. The application does not properly validate or restrict the nextPage parameter, enabling attackers to redirect users to arbitrary external sites. This vulnerability can be exploited for phishing, credential theft, malware distribution, and social engineering by leveraging the trusted WeGIA domain. The vulnerability has a CVSS score of 4.8 (medium severity) and does not require authentication but does require user interaction. No known exploits are currently reported in the wild.

Impact

For European organizations, especially charitable institutions using WeGIA, this vulnerability poses a risk of social engineering attacks that can lead to phishing, credential compromise, and malware infections. Since WeGIA is used to manage sensitive data and operations for charities, exploitation could undermine trust in these organizations and potentially lead to data breaches or financial fraud. The open redirect can be used to bypass security filters and convince users to visit malicious sites under the guise of a trusted domain, increasing the effectiveness of attacks. Although the vulnerability does not directly compromise system integrity or availability, the indirect consequences of successful phishing or malware campaigns can be severe, including reputational damage and regulatory penalties under GDPR if personal data is compromised. The medium severity indicates a moderate risk, but the impact can be amplified depending on the scale of deployment and user awareness.

CWE-601URL Redirection to Untrusted Site ('Open Redirect') (opens in a new tab)
Base weaknessLikelihood of exploit: LowOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a redirect.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design
Use an intermediate disclaimer page that provides the user with a clear warning that they are leaving the current site. Implement a long timeout before the redirect occurs, or force the user to click on the link. Be careful to avoid XSS problems (CWE-79) when generating the disclaimer page.
Architecture and Design · Enforcement by Conversion
When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
OWASP Cheat Sheets
Mass Assignment (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V5.1.5 (opens in a new tab)
Attack patterns
Cross-Site Flashing (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Jan 2026, 20:37 UTC

WeaknessesCWE-601

Technical details

References

Community reviews

Related threats