CVE-2026-52774

MEDIUMPre-NVD 6.16.1
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 6.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (51st 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-71806 (ENISA EUVD) · GHSA-r5xw-gcgw-hwp5 (GitHub Security Advisories)Source: ENISA EUVD

6.1EG
EchelonGraph verdictPlan a fixRemediate 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.7%CVSS: 6.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

YesWiki is a wiki system written in PHP. Prior to version 4.6.6, YesWiki's Bazar widget handler reflects the id GET parameter into HTML attributes using strip_tags() only. Because strip_tags() does not escape double quotes, an attacker can break out of the attribute value, inject an event handler such as onmouseover, and execute arbitrary JavaScript in the victim's browser. This issue is reachable without authentication. During validation, the vulnerable widget route returned the injected HTML for both /HomePage/widget?id=... and /NoSuchPage/widget?id=..., which shows that no login, no page ownership, no edit rights, and not even a valid page tag were required. The only routing prerequisite observed was that the Bazar extension is enabled and the request includes an id parameter. This issue has been patched in version 4.6.6.

CVSS v3
6.1
EG Score
6.1MEDIUMmedium confidence
EG Risk
43
EG Risk 43/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.
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 available. Apply it within your standard update timelines.
EPSS PROB
0.7%
EPSS %ILE
51st
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.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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).

A fix is available. Apply it within your standard update timelines.

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

July 9, 2026

Last Modified

September 8, 2026

Advisory Details (3)

Auto-updated Sep 5, 2026
Patch available. Sources: github, github_commit, github_release.
GitHub release Patch Available

v4.6.6

Patch available: YesWiki/yeswiki v4.6.6

https://github.com/YesWiki/yeswiki/releases/tag/v4.6.6
GitHub commit Patch Available

commit 1aa2710c7505 (YesWiki/yeswiki)

Patch available: YesWiki/yeswiki v4.6.6 (contains commit 1aa2710c7505)

https://github.com/YesWiki/yeswiki/commit/1aa2710c7505630b858f2142a65f9441bfaba2b2
GitHub advisoryMentions a patch (unverified)

Reflected XSS via Unescaped `id` Parameter in Bazar Widget HTML Attributes in YesWiki · Advisory · YesWiki/yeswiki · GitHub

https://github.com/YesWiki/yeswiki/security/advisories/GHSA-r5xw-gcgw-hwp5

Vendor Advisories for CVE-2026-52774(1)

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

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFix by version rangeDependents
yeswiki/yeswiki4.2.3 ... v4.6.5 (31 versions)
  • every version up to 4.6.6: fixed in 4.6.6
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 39× 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:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  2. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  3. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  4. 2026-10-25 14:21 UTCEG score recompute
  5. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  6. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  7. 2026-10-22 22:53 UTCEG score recompute
  8. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  9. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  10. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  11. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  12. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  13. 2026-10-18 03:32 UTCEG score recompute
  14. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  15. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  16. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  17. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  18. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  19. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  20. 2026-10-12 15:58 UTCEG score recompute
  21. 2026-10-11 19:41 UTCEG score recompute
  22. 2026-10-11 16:56 UTCEG score recompute
  23. 2026-10-11 14:19 UTCEG score recompute
  24. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  25. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 50th percentile
Show 42 more
  1. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  2. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  3. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  4. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  5. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  6. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  7. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  8. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  9. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  10. 2026-10-01 16:01 UTCEG score recompute
  11. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  12. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  13. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  14. 2026-09-28 10:26 UTCEG score recompute
  15. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  16. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  17. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  18. 2026-09-24 11:23 UTCEG score recompute
  19. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  20. 2026-09-23 05:53 UTCEG score recompute
  21. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  22. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  23. 2026-09-18 05:34 UTCEG score recompute
  24. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  25. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  26. 2026-09-14 07:48 UTCEG score recompute
  27. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  28. 2026-09-13 08:17 UTCEG score recompute
  29. 2026-09-12 03:21 UTCEG score recompute
  30. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  31. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  32. 2026-09-08 22:53 UTCEG score recompute
  33. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  34. 2026-09-08 16:13 UTCEG score recompute
  35. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  36. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  37. 2026-09-05 23:47 UTCEG score recompute
  38. 2026-09-05 00:19 UTCEG score recompute
  39. 2026-07-30 11:14 UTCEG score recompute
  40. 2026-07-26 12:17 UTCEG score recompute
  41. 2026-07-23 03:19 UTCEG score recompute
  42. 2026-07-09 21:46 UTCEG score recompute

Public detection templates

(1 reference)

A public Nuclei detection template is referenced for this CVE. A detection template checks whether a system is affected; it is not necessarily exploit code.

  • Nucleihttp/cves/2026/CVE-2026-52774.yaml
    Published Jul 13, 2026

    YesWiki Bazar Widget - Reflected XSS via 'id' Parameter

    Open source ↗

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-52774?
CVE-2026-52774 is a medium-severity vulnerability; its CVE record was published on July 9, 2026. YesWiki is a wiki system written in PHP. Prior to version 4.6.6, YesWiki's Bazar widget handler reflects the id GET parameter into HTML attributes using striptags() only. Because striptags() does not escape double quotes, an attacker can break out of the attribute value, inject an event handler…
When was the CVE record for CVE-2026-52774 published?
The CVE record for CVE-2026-52774 was published on July 9, 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 September 8, 2026; the record at its source may have been updated since.
Is CVE-2026-52774 actively exploited?
CVE-2026-52774 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-52774?
CVE-2026-52774 has a CVSS base score of 6.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-52774?
A fix for CVE-2026-52774 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-52774 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-52774

Explore →

Is Your Infrastructure Affected by CVE-2026-52774?

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

Book a Demo →Browse All CVEs