Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-54670 – Unauthenticated Access & Path Traversal (RCE risk) – WeGIA ≤ 3.8.4

Be the first to know when new zero-days emerge:

Summary

CVE-2026-54670 is a critical vulnerability in WeGIA, an open-source web management platform used by charitable institutions, that allows unauthenticated attackers to bypass authorization checks and perform path traversal / local file inclusion through the contribution management controller. The flaw combines a missing-authentication check (CWE-306) with insufficient input validation on controller/method names (CWE-22), letting remote attackers access sensitive financial and donor data or include arbitrary files without any credentials. It carries a CVSS v3.1 base score of 9.1 (Critical).

Technical details

  • Root cause: The request dispatcher in /html/contribuicao/controller/control.php explicitly exempts the ContribuicaoLogController from the application’s authentication check, so any request targeting that controller executes without a valid session.
  • Input validation gap: Unlike the main control.php, which enforces a whitelist of over 50 valid controller/method combinations, the contribution dispatcher only sanitizes attacker-supplied nomeClasse (controller) and metodo (method) parameters with htmlspecialchars(), rather than restricting them to an allowlist.
  • Path traversal: Because the controller name is used to build a file inclusion path without canonicalization or restriction, attackers can supply traversal sequences to include files outside the intended directory.
  • Attack vector: Network-based, no authentication or user interaction required (AV:N/AC:L/PR:N/UI:N).
  • Impact: Unauthenticated attackers can invoke sensitive methods (e.g., getContribuicoesLogJSON, sincronizarStatus) to disclose donation/contribution records containing PII and financial data, trigger payment-gateway synchronization or fraudulent billing operations, and potentially read files containing database credentials or source code via the path traversal flaw. NVD/CVSS scoring reflects high confidentiality and integrity impact with no availability impact (C:H/I:H/A:N).

Affected software

  • WeGIA (WeGIA – Web manager for charitable institutions), by LabRedesCefetRJ
  • All versions up to and including 3.8.4

Severity

  • CVSS v3.1 Base Score: 9.1 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Mitigation and recommended actions

  • Immediate: Upgrade WeGIA to version 3.8.5 or later, which fixes the authentication bypass and adds proper controller/method validation for the contribution module.
  • If immediate patching is not possible:
    • Restrict network access to the WeGIA instance (e.g., place it behind a VPN or IP allowlist) to limit exposure to trusted users only.
    • Use a web application firewall (WAF) to block requests to the contribution controller endpoint (control.php under /html/contribuicao/) that contain unexpected nomeClasse/metodo values or path traversal sequences (e.g., ../).
    • Monitor logs for unauthenticated requests to contribution-related endpoints and for anomalous file-inclusion patterns.
    • Rotate any credentials that may be stored in configuration files potentially exposed via path traversal.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge