CVE-2026-69188

HIGHPre-NVD 7.27.2
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (48th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-128183 (ENISA EUVD)Source: ENISA EUVD

7.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.2Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.2
EG Score
7.2HIGHmedium confidence
EG Risk
48
EG Risk 48/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity72% × 45%
Impact severity (EG Severity): CVSS 7.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
48th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.2): severity, escalated by confirmed exploitation. This CVE's 7.2 is its impact severity (EG Severity), not escalated.

EG Severity
7.2 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 17, 2026

Last Modified

November 18, 2026

Advisory Details (4)

Auto-updated Nov 18, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_pr, github_release.
GitHub release Patch Available

3.9.0

Patch available: LabRedesCefetRJ/WeGIA 3.9.0

https://github.com/LabRedesCefetRJ/WeGIA/releases/tag/3.9.0
GitHub commit Patch Available

commit 620ed2997ead (LabRedesCefetRJ/WeGIA)

Patch available: LabRedesCefetRJ/WeGIA 3.9.0 (contains commit 620ed2997ead)

https://github.com/LabRedesCefetRJ/WeGIA/commit/620ed2997ead2c7da6829e5b70dd0b81e2a2f98e
GitHub pull request Patch Available

Securities jv 2026 06 23

Patch available: LabRedesCefetRJ/WeGIA 3.9.0 (PR #1892 merged 2026-06-24)

https://github.com/LabRedesCefetRJ/WeGIA/pull/1892
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

RCE via Backup Upload and `phar://` Controller Inclusion · Advisory · LabRedesCefetRJ/WeGIA · GitHub

https://github.com/LabRedesCefetRJ/WeGIA/security/advisories/GHSA-vxf4-mrgm-vp43

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 7× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 23:26 UTCOSV refresh
  2. 2026-11-21 16:40 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  3. 2026-11-20 16:38 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  4. 2026-11-19 16:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  5. 2026-11-18 18:42 UTCEchelonGraph re-scored
  6. 2026-11-18 18:29 UTCEchelonGraph re-scored
  7. 2026-11-18 17:48 UTCEchelonGraph re-scored
  8. 2026-11-18 16:35 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  9. 2026-11-17 23:13 UTCENISA EUVD ID recordedEUVD-2026-128183 · Source: ENISA EUVD
  10. 2026-11-17 22:30 UTCEchelonGraph re-scored
  11. 2026-11-17 21:43 UTCEchelonGraph re-scoredFirst assessed: 7.2 HIGH
  12. 2026-11-17 21:43 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-69188?
CVE-2026-69188 is a high-severity vulnerability; its CVE record was published on November 17, 2026. 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…
When was the CVE record for CVE-2026-69188 published?
The CVE record for CVE-2026-69188 was published on November 17, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 18, 2026; the record at its source may have been updated since.
Is CVE-2026-69188 actively exploited?
CVE-2026-69188 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-69188?
CVE-2026-69188 has a CVSS base score of 7.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-69188?
A fix for CVE-2026-69188 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-69188

Explore →

Is Your Infrastructure Affected by CVE-2026-69188?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.