Cross-Site Scripting (XSS) in Alteryx Server (CVE-2023-26961)
Summary
Cross-site scripting in Alteryx Server (CVE-2023-26961). Risk of unauthorized operations or information disclosure. Exploitable via PUT /gallery/api/media.
Original description
The description as published by the source.
Alteryx Server 2022.1.1.42590 does not employ file type verification for uploaded files. This vulnerability allows attackers to upload arbitrary files (e.g., JavaScript content for stored XSS) via the type field in a JSON document within a PUT /gallery/api/media request.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2023-26961 has been found in Alteryx Server.
Attackers can target a specific entry point like PUT /gallery/api/media over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Alteryx Server CVE-2023-26961" on the vendor's site.
CVE-2023-26961 (Alteryx Server) — CWE-79 / CVSS v3 4.8
Attack vector: remote (network-reachable)
Attack surface: PUT /gallery/api/media
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.
Cross-site scripting (XSS) (CWE-79) exists in Alteryx Server. Attackers reach the vulnerable code path via PUT /gallery/api/media.
Check the vendor advisory for the affected versions of Alteryx Server. Attack surface: PUT /gallery/api/media.
Severity: Medium (CVSS 4.8/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual PUT /gallery/api/media requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Alteryx Server を使っているサービスとバージョンを洗い出す。
-
2Hunt for indicators of compromise detect
grep 'PUT /gallery/api/media' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
PUT /gallery/api/mediaへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against PUT /gallery/api/media on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- exploit gist.github.com
- patch alteryx.com