CVE-2026-130850

MEDIUMPre-NVD 5.45.4
EchelonGraph scoreHIGH confidence

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

Score 5.4 from GitHub Security Advisory (severity: MODERATE) published 2026-11-17. A secondary CVSS source baseline 5.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-127252 (ENISA EUVD) · GHSA-7887-6pww-ppxw (GitHub Security Advisories)Source: ENISA EUVD

5.4EG
EchelonGraph verdictPlan mitigationNo release containing the referenced fix is confirmed: check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule (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.3%CVSS: 5.4Exploit: No code on recordExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

LaraCollab through 0.18.2 contains a stored cross-site scripting vulnerability that allows authenticated client-role users to inject script by posting unsanitized task comments rendered via dangerouslySetInnerHTML. Attackers can post malicious comments that execute when users, including administrators, open the task or view dashboard recent comments, allowing actions in their session.

CVSS v3
5.4
EG Score
5.4MEDIUMhigh confidence
EG Risk
40
EG Risk 40/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)
Severity54% × 45%
Impact severity (EG Severity): CVSS 5.4 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 or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (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 referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule.
EPSS PROB
0.3%
EPSS %ILE
27th
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 (5.4): severity, escalated by confirmed exploitation. This CVE's 5.4 is its impact severity (EG Severity), not escalated.

EG Severity
5.4 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; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.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 or medium mission impact; Track* at high (mission-essential systems).

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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

November 17, 2026

Last Modified

November 18, 2026

Advisory Details (6)

Auto-updated Nov 18, 2026
🔬 Proof of concept available. Fix referenced — no release confirmed yet. Sources: github, github_commit.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Stored XSS in task comments: a client-role user can run script in an admin session · Advisory · vstruhar/lara-collab · GitHub

https://github.com/vstruhar/lara-collab/security/advisories/GHSA-9qhf-r3q7-3789
Web page

LaraCollab through 0.18.2 Stored XSS via Task Comments | Advisories | VulnCheck

https://www.vulncheck.com/advisories/laracollab-through-0.18.2-stored-xss-via-task-comments
GitHub commit

commit 38ecf38b010c (vstruhar/lara-collab)

Fix landed in vstruhar/lara-collab commit 38ecf38b010c — awaiting tagged release

https://github.com/vstruhar/lara-collab/commit/38ecf38b010ceff19b5be4d9041d7ddc1e623061
Web page

lara-collab/resources/js/pages/Projects/Tasks/Drawers/Comments.jsx at 0.18.1 · vstruhar/lara-collab · GitHub

https://github.com/vstruhar/lara-collab/blob/0.18.1/resources/js/pages/Projects/Tasks/Drawers/Comments.jsx#L90
Web page

lara-collab/resources/js/pages/Dashboard/Cards/RecentComments.jsx at 0.18.1 · vstruhar/lara-collab · GitHub

https://github.com/vstruhar/lara-collab/blob/0.18.1/resources/js/pages/Dashboard/Cards/RecentComments.jsx#L61
Web page

lara-collab/app/Policies/CommentPolicy.php at 0.18.1 · vstruhar/lara-collab · GitHub

https://github.com/vstruhar/lara-collab/blob/0.18.1/app/Policies/CommentPolicy.php#L21-L24

Vendor Advisories for CVE-2026-130850(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 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 16:38 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  2. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  3. 2026-11-20 05:46 UTCEchelonGraph re-scored
  4. 2026-11-20 05:46 UTCGHSA enrichmentGHSA-7887-6pww-ppxw · GitHub severity MODERATE · GitHub CVSS 5.4
  5. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  6. 2026-11-18 17:43 UTCEchelonGraph re-scored
  7. 2026-11-18 17:43 UTCGHSA enrichmentGHSA-7887-6pww-ppxw · GitHub severity MODERATE · GitHub CVSS 5.4
  8. 2026-11-18 17:29 UTCEchelonGraph re-scored
  9. 2026-11-18 17:29 UTCGHSA enrichmentGHSA-7887-6pww-ppxw · GitHub severity MODERATE · GitHub CVSS 5.4
  10. 2026-11-18 17:08 UTCEchelonGraph re-scored
  11. 2026-11-18 17:08 UTCGHSA enrichmentGHSA-7887-6pww-ppxw · GitHub severity MODERATE · GitHub CVSS 5.4
  12. 2026-11-18 16:34 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  13. 2026-11-17 21:59 UTCEchelonGraph re-scored
  14. 2026-11-17 21:59 UTCGHSA enrichmentGHSA-7887-6pww-ppxw · GitHub severity MODERATE · GitHub CVSS 5.4
  15. 2026-11-17 21:03 UTCENISA EUVD ID recordedEUVD-2026-127252 · Source: ENISA EUVD
  16. 2026-11-17 20:29 UTCEchelonGraph re-scored
  17. 2026-11-17 19:55 UTCEchelonGraph re-scoredFirst assessed: 5.4 MEDIUM
  18. 2026-11-17 19:52 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-130850?
CVE-2026-130850 is a medium-severity vulnerability; its CVE record was published on November 17, 2026. LaraCollab through 0.18.2 contains a stored cross-site scripting vulnerability that allows authenticated client-role users to inject script by posting unsanitized task comments rendered via dangerouslySetInnerHTML. Attackers can post malicious comments that execute when users, including…
When was CVE-2026-130850 made public?
CVE-2026-130850 was made public on November 17, 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 November 17, 2026. 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-130850 actively exploited?
CVE-2026-130850 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-130850?
CVE-2026-130850 has a CVSS base score of 5.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-130850?
A fix for CVE-2026-130850 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation. The vendor advisories EchelonGraph has for CVE-2026-130850 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-130850?

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