Cross-Site Scripting (XSS) in YesWiki (CVE-2026-104461)
Summary
Cross-site scripting in YesWiki (CVE-2026-104461). Risk of unauthorized operations or information disclosure. Exploitable via POST /api/entries/{formId}.
Original description
The description as published by the source.
YesWiki before 4.6.7 contains a stored cross-site scripting vulnerability in the Bazar FileField, which validates only the upload's file extension and never calls HtmlPurifierService::cleanFile, so SVG files are stored verbatim and served inline as image/svg+xml. Authenticated users can submit entries via POST /api/entries/{formId} with SVG files containing script that executes in the wiki origin when the file is opened, enabling administrator session or account compromise.
Source: NIST National Vulnerability Database NVD GitHub Advisory
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-2026-104461 has been found in YesWiki.
Attackers can target a specific entry point like POST /api/entries/{formId} over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "YesWiki CVE-2026-104461" on the vendor's site.
CVE-2026-104461 (YesWiki) — CWE-79 / CVSS v3 5.4
Attack vector: remote (network-reachable)
Attack surface: POST /api/entries/{formId}
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 YesWiki. Attackers reach the vulnerable code path via POST /api/entries/{formId}.
Check the vendor advisory for the affected versions of YesWiki. Attack surface: POST /api/entries/{formId}.
Severity: Medium (CVSS 5.4/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 POST /api/entries/{formId} requests with malformed payloads or SQL meta-characters. Run grep -r 'YesWiki' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'YesWiki' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
YesWikiを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /api/entries/{formId}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/entries/{formId}への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against POST /api/entries/{formId} on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- web github.com
- web disclosure@vulncheck.com
- web nvd.nist.gov
- web github.com