Cross-Site Scripting (XSS) in AntSword (CVE-2026-43892)
Summary
Cross-site scripting in AntSword (CVE-2026-43892). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2.1.16 or later.
Original description
The description as published by the source.
AntSword is a cross-platform website management toolkit. Prior to 2.1.16, incomplete noxss() sanitization leads to 1-click RCE via jquery.terminal format code injection. This vulnerability is fixed in 2.1.16.
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-2026-43892 has been found in AntSword.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade AntSword to 2.1.16 or later.
If unsure, ask your IT team or search "AntSword CVE-2026-43892" on the vendor's site.
CVE-2026-43892 (AntSword) — CWE-79 / CVSS v3 8.8
Attack vector: remote (network-reachable) / unauthenticated
Patched: 2.1.16 — 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.
Cross-site scripting (XSS) (CWE-79) exists in AntSword.
Check the vendor advisory for the affected versions of AntSword.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to 2.1.16.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'AntSword' . 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 'AntSword' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
AntSwordを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade AntSword to 2.1.16ステージング環境で 2.1.16 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。