Skip to main content
Menu
CVEs

CVE

WeGIA: RCE via Backup Upload and phar:// Controller Inclusion

CVE-2026-69188EUVD-2026-128183

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

7.2HighCNA
Exploited
No known exploitation
Fix
Fixed in 3.9.1
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 3.9.1.

Published
Last modified
Reference
Last checked
10/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

WeGIA is a web manager for charitable institutions. Prior to 3.9.1, a user with backup-management permission can upload a crafted gzip-compressed tar archive through web/html/configuracao/importar_dump.php, after which web/controle/control.php accepts a user-controlled modulo value and combines it with nomeClasse for require_once(). By using a phar:// path to the uploaded archive and selecting the whitelisted InternoControle, whose empty resource list is treated as authorized, the user can cause an embedded controller file and its requested method to execute as the web-server process. The attack path depends on the configured BKP_DIR, and enabling phar.readonly or phar.require_hash does not prevent PHP from reading the gzip tar archive through phar://. Successful exploitation permits access to or modification of sensitive data, configuration, credentials, source files, host commands, and services reachable by the web-server account. This issue is fixed in version 3.9.1.

cve.now Index

10Pcve.now Index 10 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.2/10CVSS 7.2
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 29 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 3.9.1.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-69188 (WeGIA: RCE via Backup Upload and `phar://` Controller Inclusion), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-69188 (entry last updated 2026-11-17):
Affected:
- LabRedesCefetRJ WeGIA: fixed in 3.9.1
Fixed versions: 3.9.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-69188 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-69188 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/LabRedesCefetRJ/WeGIA/security/advisories/GHSA-vxf4-mrgm-vp43
- https://github.com/LabRedesCefetRJ/WeGIA/pull/1892
- https://github.com/LabRedesCefetRJ/WeGIA/commit/620ed2997ead2c7da6829e5b70dd0b81e2a2f98e
- https://github.com/LabRedesCefetRJ/WeGIA/releases/tag/3.9.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-69188
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-69188"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • LabRedesCefetRJ WeGIA

    fixed in 3.9.1

Evidence 6

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 3

  1. Repository
  2. Repository
  3. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-69188

Is CVE-2026-69188 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-69188?

WeGIA: before 3.9.1.Source: cve.now feed data

How do I fix CVE-2026-69188?

Upgrade to a fixed version: 3.9.1.Source: cve.now feed data

More CVEs