VulnerabilityPublished 13 Oct 2025

CVE-2025-62361: LabRedesCefetRJ WeGIA · Open Redirect

Affects LabRedesCefetRJ WeGIASource CVE Database V5

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

Data as of 26 Oct 2026, 10:12 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 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.5.0

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 13 Oct 2025
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 or the CVSS exploit maturity 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 LabRedesCefetRJ WeGIA to 3.5.0.

Affected software

Product	Affected	Fixed in
LabRedesCefetRJ WeGIA	Affected <3.5.0	Fixed in 3.5.0

AI-suggested

Upgrade all WeGIA installations to version 3.5.0 or later, where the open redirect vulnerability is fixed.
Implement strict input validation and URL whitelisting on the nextPage parameter to ensure redirection only occurs to internal, trusted URLs.
Deploy web application firewalls (WAFs) with rules to detect and block suspicious redirect attempts or anomalous URL parameters.
Conduct user awareness training focused on recognizing phishing attempts, especially those involving suspicious redirects from trusted domains.
Monitor web server logs and network traffic for unusual redirect patterns or spikes in external URL requests originating from WeGIA.
Consider implementing multi-factor authentication (MFA) to reduce the impact of credential theft resulting from phishing.
Regularly audit and update all third-party components and dependencies to minimize exposure to known vulnerabilities.
Establish incident response procedures to quickly address phishing or malware incidents linked to this vulnerability. These steps go beyond generic advice by focusing on both technical fixes and organizational preparedness tailored to the nature of this open redirect issue.

Description

WeGIA is an open source Web Manager for Institutions with a focus on Portuguese language users. Prior to 3.5.0, an Open Redirect vulnerability was identified in the control.php endpoint of the WeGIA application, specifically in the nextPage parameter (metodo=listarTodos nomeClasse=AlmoxarifeControle). This vulnerability allows attackers to redirect users to arbitrary external domains, enabling phishing campaigns, malicious payload distribution, or user credential theft. This vulnerability is fixed in 3.5.0.

Impact

For European organizations using WeGIA, this vulnerability presents a moderate risk primarily through social engineering and phishing attacks. Attackers can exploit the open redirect to craft convincing URLs that appear to originate from a trusted institutional domain, increasing the success rate of credential theft or malware delivery. This can lead to compromised user accounts, unauthorized access to sensitive institutional data, and potential lateral movement within networks. The impact on confidentiality and integrity is limited but non-negligible, as attackers do not directly gain system access but can leverage stolen credentials or malware payloads. Availability impact is minimal. Given the focus on Portuguese language users, institutions in European countries with significant Portuguese-speaking populations or academic/cultural ties to Brazil and Portugal may be more targeted. The medium severity rating suggests that while the vulnerability is not critical, it should not be ignored, especially in sectors like education, research, and public administration where WeGIA is deployed. Failure to patch could facilitate targeted phishing campaigns against staff and students, potentially leading to broader security incidents.

Summary

CVE-2025-62361 identifies an Open Redirect vulnerability (CWE-601) in the WeGIA web management system developed by LabRedesCefetRJ, primarily targeting Portuguese language institutions. The vulnerability resides in the nextPage parameter of the control.php endpoint, which fails to properly validate or sanitize user-supplied URLs. Attackers can exploit this by crafting URLs that redirect users from the legitimate WeGIA domain to arbitrary external websites. Such redirection can be leveraged in phishing campaigns to trick users into divulging credentials or downloading malware, exploiting the trust users place in the original domain. The vulnerability does not require authentication but does require user interaction, such as clicking a malicious link. The CVSS 4.8 score reflects medium severity, considering the network attack vector, low complexity, no privileges required, but user interaction needed and limited impact on confidentiality and integrity. The vulnerability affects all versions prior to 3.5.0, which includes many deployments that have not yet upgraded. Although no known exploits have been reported in the wild, the vulnerability's nature makes it a viable vector for social engineering attacks. The issue is resolved in WeGIA version 3.5.0 by properly validating the nextPage parameter to restrict redirection only to trusted internal pages. Organizations using WeGIA should verify their version and apply the update promptly. Additionally, monitoring for suspicious URL patterns and educating users about phishing risks can reduce exploitation likelihood.

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 21 Oct 2025, 00:39 UTC

WeaknessesCWE-601

Technical details

References

Community reviews

Related threats