CVE-2026-116217

MEDIUMPre-NVD 6.16.1
EchelonGraph scoreHIGH confidence

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

Score 6.1 from GitHub Security Advisory published 2026-10-26. The CNA's CVSS baseline 6.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, GitHub Security Advisory
Trending — 5 sources updated this week

Also known asEUVD-2026-109809 (ENISA EUVD) · GHSA-p567-rgff-v7fc (GitHub Security Advisories)Source: ENISA EUVD

6.1EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

RosarioSIS before 12.9.2 contains a reflected cross-site scripting vulnerability in modules/Food_Service/MenuReports.php that allows unauthenticated attackers to inject attributes via unescaped menu_id and modname parameters. Attackers can lure a logged-in administrator to a crafted Modules.php link whose double-quoted menu_id injects an onmouseover handler, stealing session and CSRF tokens to act as the administrator.

CVSS v3
6.1
EG Score
6.1MEDIUMhigh confidence
EG Risk
42
EG Risk 42/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)
Severity61% × 45%
Impact severity (EG Severity): CVSS 6.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0% × 40%
No KEV listing, EG-KEV tier or EPSS when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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.3%
EPSS %ILE
20th
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 (6.1): severity, escalated by confirmed exploitation. This CVE's 6.1 is its impact severity (EG Severity), not escalated.

EG Severity
6.1 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% 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 or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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

October 26, 2026

Last Modified

October 26, 2026

Advisory Details (4)

Auto-updated Oct 26, 2026
Patch available. Sources: github_commit.
Web page

GitHub - francoisjacquet/rosariosis: RosarioSIS Student Information System for school management. · GitHub

https://github.com/francoisjacquet/rosariosis
Web page

rosariosis/modules/Food_Service/MenuReports.php at v12.9.1 · francoisjacquet/rosariosis · GitHub

https://github.com/francoisjacquet/rosariosis/blob/v12.9.1/modules/Food_Service/MenuReports.php#L315
Web page

Security fix #390 Reflected XSS - unescaped reflection into `<form action>` (08c871da) · Commits · François Jacquet / rosariosis · GitLab

https://gitlab.com/francoisjacquet/rosariosis/-/commit/08c871da7f9d8478e0e72d104b310b98630fc755
GitHub commit Patch Available

commit 08c871da7f9d (francoisjacquet/rosariosis)

Patch available: francoisjacquet/rosariosis v12.9.2 (contains commit 08c871da7f9d)

https://github.com/francoisjacquet/rosariosis/commit/08c871da7f9d8478e0e72d104b310b98630fc755

Vendor Advisories for CVE-2026-116217(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 11× 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 it from the CNA feed. 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). Most recent first.

  1. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  2. 2026-10-26 17:59 UTCEG score recompute
  3. 2026-10-26 17:59 UTCGHSA enrichmentGHSA-p567-rgff-v7fc · GitHub CVSS 6.1
  4. 2026-10-26 17:33 UTCEG score recompute
  5. 2026-10-26 17:33 UTCGHSA enrichmentGHSA-p567-rgff-v7fc · GitHub CVSS 6.1
  6. 2026-10-26 16:32 UTCEG score recompute
  7. 2026-10-26 16:32 UTCGHSA enrichmentGHSA-p567-rgff-v7fc · GitHub CVSS 6.1
  8. 2026-10-26 15:01 UTCENISA EUVD ID recordedEUVD-2026-109809 · Source: ENISA EUVD
  9. 2026-10-26 14:41 UTCEG score recompute
  10. 2026-10-26 14:02 UTCEG score recomputeFirst assessed: 6.1 MEDIUM
  11. 2026-10-26 14:00 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-116217?
CVE-2026-116217 is a medium-severity vulnerability; its CVE record was published on October 26, 2026. RosarioSIS before 12.9.2 contains a reflected cross-site scripting vulnerability in modules/FoodService/MenuReports.php that allows unauthenticated attackers to inject attributes via unescaped menuid and modname parameters. Attackers can lure a logged-in administrator to a crafted Modules.php link…
When was CVE-2026-116217 made public?
CVE-2026-116217 was made public on July 16, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on October 26, 2026. EchelonGraph's copy of the record carries a last-modified date of October 26, 2026; the record at its source may have been updated since.
Is CVE-2026-116217 actively exploited?
CVE-2026-116217 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-116217?
CVE-2026-116217 has a CVSS base score of 6.1 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-116217?
A fix for CVE-2026-116217 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-116217 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-116217?

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