CVE-2026-49279

HIGHPre-NVD 7.77.7
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (34th 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
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-44825 (ENISA EUVD) · GHSA-2fhx-q92v-5fhv (GitHub Security Advisories)Source: ENISA EUVD

7.7EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (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.4%CVSS: 7.7Exploit: No code on recordExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

WWBN AVideo is an open source video platform. Versions 29.0 and below contain a Stored XSS vulnerability through the autoEvalCodeOnHTML parameter in the MessageSQLite WebSocket Handler. The MessageSQLite.php handler only strips autoEvalCodeOnHTML from $json['msg'], but msgToResourceId() reads from $msg['json'] with higher priority. An attacker can place the XSS payload in the json key instead of msg, bypassing the sanitization entirely. An authenticated attacker can execute arbitrary JavaScript in any connected user's browser session via the WebSocket messaging system, stealing session cookies and authentication tokens, taking over accounts through session hijacking, and chaining with CSRF to perform admin actions on the victim's behalf, in the default SQLite WebSocket backend configuration. This issue has a patch that has yet to be officially released, see https://github.com/WWBN/AVideo/commit/3e0b3ce2bfa766183ff0ae227439394db57b1a23.

CVSS v3
7.7
EG Score
7.7HIGHmedium confidence
EG Risk
51
EG Risk 51/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)
Severity77% × 45%
Impact severity (EG Severity): CVSS 7.7 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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
34th
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.7): severity, escalated by confirmed exploitation. This CVE's 7.7 is its impact severity (EG Severity), not escalated.

EG Severity
7.7 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.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). 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.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; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

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.

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

June 4, 2026

Last Modified

October 24, 2026

Advisory Details (2)

Auto-updated Jul 15, 2026
No fix on record yet. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Stored XSS via autoEvalCodeOnHTML in MessageSQLite WebSocket Handler · Advisory · WWBN/AVideo · GitHub

https://github.com/WWBN/AVideo/security/advisories/GHSA-2fhx-q92v-5fhv
GitHub commit

commit 3e0b3ce2bfa7 (WWBN/AVideo)

Fix landed in WWBN/AVideo commit 3e0b3ce2bfa7 — awaiting tagged release

https://github.com/WWBN/AVideo/commit/3e0b3ce2bfa766183ff0ae227439394db57b1a23

Vendor Advisories for CVE-2026-49279(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
composerwwbn/avideo—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFix by version rangeDependents
wwbn/avideo10.4 ... 29.0 (18 versions)
  • every version through 29.0: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 42× 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.

Showing the most recent 100 of 190 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 90 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  2. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  3. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  4. 2026-10-27 21:01 UTCEG score recompute
  5. 2026-10-27 21:01 UTCGHSA enrichmentGHSA-2fhx-q92v-5fhv · GitHub severity HIGH
  6. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  7. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  8. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  9. 2026-10-25 14:22 UTCEG score recompute
  10. 2026-10-24 21:26 UTCEG score recompute
  11. 2026-10-24 21:26 UTCGHSA enrichmentGHSA-2fhx-q92v-5fhv · GitHub severity HIGH
  12. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  13. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  14. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  15. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  16. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  17. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  18. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  19. 2026-10-18 03:34 UTCEG score recompute
  20. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  21. 2026-10-17 12:00 UTCEG score recompute
  22. 2026-10-17 12:00 UTCGHSA enrichmentGHSA-2fhx-q92v-5fhv · GitHub severity HIGH
  23. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  24. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  25. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
Show 75 more
  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  3. 2026-10-12 16:00 UTCEG score recompute
  4. 2026-10-11 19:43 UTCEG score recompute
  5. 2026-10-11 16:57 UTCEG score recompute
  6. 2026-10-11 14:21 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  10. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  11. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  12. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  13. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  14. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  15. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  16. 2026-10-03 12:09 UTCOSV refresh
  17. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  18. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  19. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  20. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  21. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  22. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  23. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  24. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  25. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  26. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  27. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  28. 2026-09-14 05:22 UTCEG score recompute
  29. 2026-09-14 05:22 UTCGHSA enrichmentGHSA-2fhx-q92v-5fhv · GitHub severity HIGH
  30. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  31. 2026-09-12 23:36 UTCOSV refresh
  32. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  33. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  34. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  35. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  36. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  37. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  38. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  39. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  40. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  41. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  42. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  43. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  44. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  45. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  46. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  47. 2026-08-25 03:28 UTCEG score recompute
  48. 2026-08-25 03:28 UTCGHSA enrichmentGHSA-2fhx-q92v-5fhv · GitHub severity HIGH
  49. 2026-08-23 12:41 UTCEG score recompute
  50. 2026-08-23 12:41 UTCGHSA enrichmentGHSA-2fhx-q92v-5fhv · GitHub severity HIGH
  51. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  52. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  53. 2026-08-21 14:36 UTCGHSA enrichmentGHSA-2fhx-q92v-5fhv · GitHub severity HIGH
  54. 2026-08-20 23:04 UTCEG score recompute
  55. 2026-08-20 23:04 UTCGHSA enrichmentGHSA-2fhx-q92v-5fhv · GitHub severity HIGH
  56. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  57. 2026-08-20 09:56 UTCEG score recompute
  58. 2026-08-20 09:56 UTCGHSA enrichmentGHSA-2fhx-q92v-5fhv · GitHub severity HIGH
  59. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  60. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  61. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  62. 2026-08-17 06:42 UTCGHSA enrichmentGHSA-2fhx-q92v-5fhv · GitHub severity HIGH
  63. 2026-08-16 16:25 UTCEG score recompute
  64. 2026-08-16 16:25 UTCGHSA enrichmentGHSA-2fhx-q92v-5fhv · GitHub severity HIGH
  65. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  66. 2026-08-16 03:22 UTCEG score recompute
  67. 2026-08-16 03:22 UTCGHSA enrichmentGHSA-2fhx-q92v-5fhv · GitHub severity HIGH
  68. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  69. 2026-08-15 14:20 UTCEG score recompute
  70. 2026-08-15 14:20 UTCGHSA enrichmentGHSA-2fhx-q92v-5fhv · GitHub severity HIGH
  71. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  72. 2026-08-15 00:43 UTCGHSA enrichmentGHSA-2fhx-q92v-5fhv · GitHub severity HIGH
  73. 2026-08-14 11:41 UTCGHSA enrichmentGHSA-2fhx-q92v-5fhv · GitHub severity HIGH
  74. 2026-08-13 22:38 UTCEG score recompute
  75. 2026-08-13 22:38 UTCGHSA enrichmentGHSA-2fhx-q92v-5fhv · GitHub severity HIGH

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-49279?
CVE-2026-49279 is a high-severity vulnerability; its CVE record was published on June 4, 2026. WWBN AVideo is an open source video platform. Versions 29.0 and below contain a Stored XSS vulnerability through the autoEvalCodeOnHTML parameter in the MessageSQLite WebSocket Handler. The MessageSQLite.php handler only strips autoEvalCodeOnHTML from $json['msg'], but msgToResourceId() reads from…
When was the CVE record for CVE-2026-49279 published?
The CVE record for CVE-2026-49279 was published on June 4, 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 October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-49279 actively exploited?
CVE-2026-49279 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-49279?
CVE-2026-49279 has a CVSS base score of 7.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-49279?
No fix for CVE-2026-49279 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-49279 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-49279

Explore →

Is Your Infrastructure Affected by CVE-2026-49279?

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

Book a Demo →Browse All CVEs