CVE-2026-50742

MEDIUMNVD 5.45.4
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.4 under NVD CVSS v3. EPSS exploit probability: 0.3% (27th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 4.4 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-06-26) is not newer than that change (2026-10-25), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2026-39603 (ENISA EUVD) · GHSA-q7h4-cw8q-5rmq (GitHub Security Advisories)Source: ENISA EUVD

5.4EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.4Exploit: None knownExposed services: Not assessed

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

The CVE record's CNA (HackerOne) lists Revive Adserver versions up to and including 6.0.7 as affected. No release containing a fix is confirmed on record.

A stored XSS vulnerabilities exists in the maintenance-acl-check.php and maintenance-banners-check.php tools of Revive Adserver 6.0.7. The issue was caused by entity names being displayed without proper escaping when inconsistencies were detected. Whether the XSS payload is executed when an administrator uses the affected maintenance tools is not entirely under the attacker's control.

CVSS v3
5.4
EG Score
5.4MEDIUMmedium confidence
EG Risk
24
EG Risk 24/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.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (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.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.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). 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 every mission impact level.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 every mission impact level.

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 none (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 26, 2026

Last Modified

October 25, 2026

Advisory Details (1)

Auto-updated Jun 26, 2026
No fix on record yet.
Web page

HackerOne

https://hackerone.com/reports/3781311

Vendor Advisories for CVE-2026-50742(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 12× in last 7d / 40× 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 217 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 117 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-50742?
CVE-2026-50742 is a medium-severity vulnerability; its CVE record was published on June 26, 2026. A stored XSS vulnerabilities exists in the maintenance-acl-check.php and maintenance-banners-check.php tools of Revive Adserver 6.0.7. The issue was caused by entity names being displayed without proper escaping when inconsistencies were detected. Whether the XSS payload is executed when an…
When was the CVE record for CVE-2026-50742 published?
The CVE record for CVE-2026-50742 was published on June 26, 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 25, 2026; the record at its source may have been updated since.
Is CVE-2026-50742 actively exploited?
CVE-2026-50742 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-50742?
CVE-2026-50742 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-50742?
No fix for CVE-2026-50742 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 CVE record's CNA (HackerOne) lists Revive Adserver versions up to and including 6.0.7 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-50742 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-50742?

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

Book a Demo →Browse All CVEs