CVE-2026-35472
Received Received - Intake
Open Redirect in WeGIA control.php Enables Phishing Attacks

Publication date: 2026-04-06

Last updated on: 2026-04-09

Assigner: GitHub, Inc.

Description
WeGIA is a Web manager for charitable institutions. Prior to 3.6.9, an Open Redirect vulnerability was identified in the /WeGIA/controle/control.php endpoint of the WeGIA application, specifically through the nextPage parameter when combined with metodo=listarTodos and nomeClasse=EstoqueControle. The application fails to validate or restrict the nextPage parameter, allowing attackers to redirect users to arbitrary external websites. This can be abused for phishing attacks, credential theft, malware distribution, and social engineering using the trusted WeGIA domain. This vulnerability is fixed in 3.6.9.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-04-06
Last Modified
2026-04-09
Generated
2026-05-07
AI Q&A
2026-04-07
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
wegia wegia to 3.6.9 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-601 The web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a redirect.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

The vulnerability is an Open Redirect issue in the WeGIA web application prior to version 3.6.9. It occurs in the /WeGIA/controle/control.php endpoint through the nextPage parameter when used with metodo=listarTodos and nomeClasse=EstoqueControle. The application does not properly validate or restrict the nextPage parameter, which allows attackers to redirect users to arbitrary external websites.

This flaw can be exploited by attackers to perform phishing attacks, steal credentials, distribute malware, or conduct social engineering attacks by leveraging the trusted WeGIA domain.


How can this vulnerability impact me? :

This vulnerability can impact users by enabling attackers to redirect them to malicious external websites. Such redirects can be used for phishing attacks to steal user credentials, distribute malware, or conduct social engineering attacks.

Because the redirect occurs from a trusted domain, users may be more likely to trust the malicious links, increasing the risk of compromise.


What immediate steps should I take to mitigate this vulnerability?

To mitigate this Open Redirect vulnerability in the WeGIA application, you should upgrade the application to version 3.6.9 or later, where the issue is fixed.

Until the upgrade is applied, consider restricting or validating the nextPage parameter in the /WeGIA/controle/control.php endpoint, especially when combined with metodo=listarTodos and nomeClasse=EstoqueControle, to prevent arbitrary redirects.

Additionally, monitor user reports and logs for suspicious redirect attempts that could indicate exploitation.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The vulnerability is an Open Redirect in the WeGIA application that can be exploited for phishing, credential theft, malware distribution, and social engineering by redirecting users to arbitrary external websites.

Such exploitation can potentially lead to unauthorized disclosure of personal or sensitive information, which may impact compliance with standards and regulations like GDPR and HIPAA that require protection of user data and prevention of phishing and social engineering attacks.

However, the provided information does not explicitly state the direct impact on compliance with these standards.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This Open Redirect vulnerability can be detected by monitoring HTTP requests to the /WeGIA/controle/control.php endpoint that include the specific query parameters metodo=listarTodos and nomeClasse=EstoqueControle along with a nextPage parameter containing an external URL.

One way to detect potential exploitation attempts is to search web server logs or network traffic for requests matching this pattern.

Example commands to detect such requests in web server logs (assuming Apache logs in access.log):

  • grep '/WeGIA/controle/control.php' access.log | grep 'metodo=listarTodos' | grep 'nomeClasse=EstoqueControle' | grep 'nextPage=http'

Alternatively, using tools like tcpdump or Wireshark to filter HTTP GET requests containing these parameters can help identify exploitation attempts in real time.

  • tcpdump -A -s 0 'tcp port 80 and (((ip[2:2] - ((ip[0]&0xf)<<2)) - ((tcp[12]&0xf0)>>2)) != 0)' | grep '/WeGIA/controle/control.php'

In summary, detection involves looking for HTTP requests to the vulnerable endpoint with the specific parameters and an external URL in nextPage.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart