dbcve.org
Open RedirectWeakness · CWE-601

CVE-2026-45335

MEDIUM · 5.4 CVSS v3.1 Published 2026-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
WeGIA is a web manager for charitable institutions. Prior to 3.7.3, 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=InternoControle. 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.7.3.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

WeGIA prior to 3.7.3 contains an open redirect vulnerability in /WeGIA/controle/control.php where the nextPage parameter, when used with metodo=listarTodos and nomeClasse=InternoControle, is not validated, allowing attackers to specify arbitrary external URLs for redirection.

MitigationImplement strict validation of the nextPage parameter to either restrict redirects to relative/internal paths only or maintain a whitelist of allowed domains; ensure the fix is tested for bypass attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate WeGIA installation directory
    Search for the /WeGIA directory in your web server's document root (commonly /var/www/html, /www, or C:\inetpub\wwwroot). Verify the presence of the controle/control.php file within it.
    Affected if The WeGIA directory and the controle/control.php file exist in your web root.
  2. Identify WeGIA version
    Check version.php, version.txt, or any VERSION file in the WeGIA root directory. If unavailable, examine the control.php file header comments or any config file that stores the version number.
    Affected if The installed version is lower than 3.7.3 (e.g., 3.7.2, 3.7.1, 3.6.x, etc.).
  3. Verify vulnerable parameter combination exists
    Open /WeGIA/controle/control.php and search for code handling the 'nextPage' parameter within conditional blocks that check for 'metodo=listarTodos' and 'nomeClasse=InternoControle'. Look for statements like $_GET['nextPage'] being used in a header() or redirect function without validation.
    Affected if The code contains logic processing nextPage with metodo=listarTodos and nomeClasse=InternoControle, and the redirect destination is set directly from the user-supplied parameter without validation.
  4. Inspect redirect implementation
    In control.php, locate where the nextPage parameter is used for redirection (typically with header('Location: ' . $nextPage) or similar). Verify if there is any validation restricting it to relative paths or whitelisted domains.
    Affected if The nextPage parameter is used in a redirect without validation, allowing full URLs (http:// or https://) to be passed and followed.

You are affected if WeGIA version is prior to 3.7.3 AND the control.php file contains the vulnerable code path where the nextPage parameter is used for redirection without validation when metodo=listarTodos and nomeClasse=InternoControle are supplied.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict validation of the nextPage parameter to either restrict redirects to relative/internal paths only or maintain a whitelist of allowed domains; ensure the fix is tested for bypass attempts.

Recommended fix High confidence

WeGIA 3.7.3

  1. 1. Backup your current WeGIA installation and database before making any changes.
  2. 2. Download WeGIA version 3.7.3 from the official GitHub repository or release source.
  3. 3. Replace the existing WeGIA files with the new version 3.7.3 files.
  4. 4. Verify that the /WeGIA/controle/control.php endpoint now properly validates the nextPage parameter.
  5. 5. Test that the application redirects only to internal or whitelisted URLs, blocking external redirects.
  6. 6. Confirm all other application functionality remains operational after the upgrade.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45335 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45335 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data