Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate to Admin UI
-
ExploitSave Global Prompt with malicious event handler
-
ExecutionVictim opens prompt, stored script executes
-
ImpactHijack viewer session / phish
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires: (1) an authenticated account on the gateway with permission to create/save a Global Prompt template (PR:L); (2) the MCP Admin UI enabled - note the 0.3.1 patch changes MCPGATEWAY_UI_ENABLED and MCPGATEWAY_ADMIN_API_ENABLED to false by default, so an enabled/exposed Admin UI is the precondition; and (3) a second victim user who subsequently opens and views the attacker-saved prompt in the Admin UI (UI:P passive interaction). Limiting factors that reduce real-world risk: it is not unauthenticated, the payload only fires when another user renders the stored prompt, impact is confined to the viewer's browser session (no direct server compromise), and default-off UI settings in patched deployments remove the surface entirely. |
| Impact | This is a medium-severity stored XSS (CWE-79) in the MCP Context Forge Admin UI Global Prompts feature, and the signals point to a real-but-bounded risk rather than an urgent emergency. The input CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N, score 5.1) shows network reachability and low complexity but requires authentication (PR:L) and passive victim interaction (UI:P), with no impact to the vulnerable system itself (VC/VI/VA:N) and only limited confidentiality/integrity impact to a subsequent system (SC:L/SI:L) - i.e. the viewing user's browser session. No EPSS score, no CISA KEV listing, and no public POC were provided in the intelligence, so exploitation status is 'no public exploit identified at time of analysis'; there is no evidence of active exploitation to elevate priority. A notable mitigating signal from the patch diff is that the fixed release flips MCPGATEWAY_UI_ENABLED and MCPGATEWAY_ADMIN_API_ENABLED to false by default, meaning the Admin UI attack surface is not exposed in default post-fix deployments. Net: a legitimate issue worth patching to 0.3.1, but a second-order, authenticated, interaction-dependent XSS - not a high-urgency remote code execution. No key signals directly conflict; the main gap is the absence of EPSS/KEV/POC data, consistent with a newly disclosed medium-severity web flaw. |
| Exploit ScenarioDerived | An authenticated low-privilege user of an MCP Context Forge gateway creates a Global Prompt whose template body contains script-capable HTML event handlers. When a higher-privileged operator or another user later opens that prompt in the Admin UI, the stored markup is rendered without sufficient output encoding and the script executes in the victim's browser, letting the attacker read keystrokes, display phishing content, or act using the viewer's authenticated session. No public exploit code is identified at time of analysis, but the technique (storing an onX event handler) is trivial to reproduce. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
Stored cross-site scripting in IBM's MCP Context Forge (versions 0.2.0 up to but not including 0.3.1) lets an authenticated user who can create or save a Global Prompt store markup with script-capable event handlers, which then executes in the browser of any other user who views that saved prompt in the MCP Admin UI. Successful exploitation can rewrite the interface, display phishing content, capture keystrokes reachable by the page, and perform actions with the victim's browser session, but it requires a valid account, an enabled Admin UI, and a second user to open the prompt. There is no public exploit identified at time of analysis, no KEV listing, and the vendor-released patch in version 0.3.1 (commit acd1619, PR #337) also flips MCPGATEWAY_UI_ENABLED and MCPGATEWAY_ADMIN_API_ENABLED to false by default, removing the surface entirely for patched deployments.
RemediationAI
Upgrade to IBM MCP Context Forge 0.3.1, which is the vendor-released patch that contains the fix (commit acd16196158f9a393187551b21a2fc61650f2e3d, PR #337) as documented in advisory GHSA-x6gc-rm5j-55mw at https://github.com/IBM/mcp-context-forge/security/advisories/GHSA-x6gc-rm5j-55mw. The 0.3.1 changeset also sets MCPGATEWAY_UI_ENABLED and MCPGATEWAY_ADMIN_API_ENABLED to false in the shipped .env.example, so operators running the patched release should keep those flags disabled unless the Admin UI is genuinely required, and when it is required they should restrict it to trusted administrative networks and authenticated users only, since the flaw requires a saved Global Prompt plus a second viewer to trigger. For environments that cannot upgrade immediately, the most effective compensating control is to keep the MCP Admin UI and Admin API disabled (the default in 0.3.1 and the configuration changed in this patch), or otherwise limit access to the Global Prompts management interface to fully trusted administrators; the trade-off is loss of the web-based management console, and disabling the UI does not fix any prompts already stored. Additional hardening includes applying a Content-Security-Policy that forbids inline and event-handler script execution, which reduces but does not eliminate the stored-XSS execution path, and rotating or invalidating sessions of users who viewed attacker-controlled prompts.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The issue is a classic stored (persistent) cross-site scripting flaw, CWE-79, rooted in missing or insufficient output encoding. The affected component is the Global Prompts feature of the MCP Context Forge gateway, which persists an administrator-supplied prompt template and later re-renders it in the MCP Admin UI. Because the stored template is inserted into the DOM without proper contextual escaping, an attacker who controls the template can embed HTML attributes such as event handlers that the browser treats as executable script. The CPE identifier cpe:2.3:a:ibm:mcp-context-forge:*:*:*:*:*:*:*:* confirms IBM MCP Context Forge as the affected product family, and the vendor's own reference set (GHSA-x6gc-rm5j-55mw, PR #337, commit acd16196158f9a393187551b21a2fc61650f2e3d, release tag v0.3.1) maps the affected window from 0.2.0 to just before 0.3.1. The vulnerable behavior is therefore a server-side rendering/encoding defect rather than a flaw in the MCP protocol itself; the MCP Admin UI is the execution context and the browser session of the viewing user is the boundary of impact.
Know when Mcp Context Forge gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N
Authenticated attacker stores the payload (PR:L), a different user must render it (UI:R), execution in the victim's browser crosses a security authority (S:C) with limited C/I and no availability impact.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
1DescriptionCVE.org
MCP Context Forge provides an MCP Admin UI for managing gateway resources. From 0.2.0 until 0.3.1, the Global Prompts feature stores a prompt template without sufficient output encoding before the MCP Admin UI renders it. An authenticated attacker can save markup containing script-capable event handlers, and the code executes when another user views the saved prompt. The stored cross-site scripting can alter the interface, present phishing content, observe keystrokes available to the page, and act with the viewer's browser session. This issue is fixed in version 0.3.1.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
More in Mcp Context Forge
View allSandbox escape in the python_sandbox_server subproject of IBM MCP Context Forge (versions up to and including 1.0.1) all
Improper authentication in IBM MCP Context Forge prior to 1.0.2 allows remote, unauthenticated attackers to forge HS256-
EUVD-2026-98770
NVD
CVE.org
EPSS
Vulnrichment
GitHub
Exploit-DB