The Magee Shortcodes WordPress plugin through 2.1.1 does not sanitise and escape user input in some of its AJAX actions, which are available to unauthenticated users, before reflecting it back in the response, leading to Reflected Cross-Site Scripting.
CVE-2026-105316
HIGHPre-NVD 7.17.1—Trending — 4 sources updated this week
EchelonGraph scoreHIGH confidence
Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-10-07. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.1; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, ghsa
7.1EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 7.1Exploit: None knownExposed services: Not assessed
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
- CVSS v3
- 7.1
- EG Score
- 7.1HIGHhigh confidence
- EG Risk
- 32EG Risk 32/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity71% × 45%Exploitation0% × 40%Automatability0% × 15%CISA SSVC: Track at every mission impact level.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
- —
- EPSS %ILE
- —
- KEV
- Not listed
CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
October 7, 2026
Last Modified
October 7, 2026
Advisory Details (1)
Auto-updated Oct 7, 2026🔬 Proof of concept available. No fix on record yet.
generic🟡 PoC Available
Magee Shortcodes <= 2.1.1 – Reflected XSS via live_preview and magee_create_shortcode Actions | CVE 2026-105316 | Plugin Vulnerabilities
https://wpscan.com/vulnerability/8240033a-bb4b-490f-97da-4ae768d2cb6d/Vendor Advisories for CVE-2026-105316(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 9× in last 7d / 9× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
- 2026-10-07 15:09 UTCEG score recompute
- 2026-10-07 15:09 UTCGHSA enrichment
- 2026-10-07 10:22 UTCGHSA enrichment
- 2026-10-07 10:07 UTCEG score recompute▲ 7.10
- 2026-10-07 10:07 UTCGHSA enrichment
- 2026-10-07 10:06 UTCMITRE cvelistV5CVSS v3 → 7.1 · severity → HIGH
- 2026-10-07 07:28 UTCNVD update
- 2026-10-07 06:22 UTCEG score recompute
- 2026-10-07 06:21 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-105316?
CVE-2026-105316 is a high vulnerability published on October 7, 2026. The Magee Shortcodes WordPress plugin through 2.1.1 does not sanitise and escape user input in some of its AJAX actions, which are available to unauthenticated users, before reflecting it back in the response, leading to Reflected Cross-Site Scripting.
When was CVE-2026-105316 disclosed?
CVE-2026-105316 was first published on October 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-105316?
CVE-2026-105316 has a CVSS v3.1 base score of 7.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-105316?
No fix for CVE-2026-105316 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-105316 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-105316
Is Your Infrastructure Affected by CVE-2026-105316?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.