← Back
GHSA-x975-rgx4-5fh4
Cross-Site Scripting (XSS) in appium-mcp (GHSA-x975-rgx4-5fh4)
Summary
cross-site scripting in appium-mcp (GHSA-x975-rgx4-5fh4). Risk of unauthorized operations or information disclosure. Exploitable via ``createLocatorGeneratorUI``. Mitigation: upgrade to `1.85.10` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-x975-rgx4-5fh4** has been found in appium-mcp.
Attackers can target a specific entry point like ``createLocatorGeneratorUI`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade appium-mcp to **1.85.10** or later.
If unsure, ask your IT team or search "appium-mcp GHSA-x975-rgx4-5fh4" on the vendor's site.
GHSA-x975-rgx4-5fh4 (appium-mcp) — CWE-79 /
Attack surface: `createLocatorGeneratorUI` / `text` / `generate_locators` / `window.parent.postMessage`
Patched: `1.85.10` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**Cross-site scripting (XSS)** (CWE-79) exists in appium-mcp. Attackers reach the vulnerable code path via ``createLocatorGeneratorUI`` without authentication.
📍 Affected scope
appium-mcp — . Attack surface: `createLocatorGeneratorUI` / `text` / `generate_locators` / `window.parent.postMessage`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.85.10**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'appium-mcp' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'appium-mcp' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `appium-mcp` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade appium-mcp to 1.85.10ステージング環境で 1.85.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
appium-mcp
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.85.10"}]}]