Cross-Site Scripting (XSS) in FACTION (CVE-2026-44669)
Summary
Cross-site scripting in FACTION (CVE-2026-44669). Confidential information can be exposed externally. Mitigation: upgrade to 1.8.3 or later.
Original description
The description as published by the source.
FACTION is a PenTesting Report Generation and Collaboration Framework. Prior to 1.8.3, Faction is vulnerable to stored cross-site scripting (XSS) via attachment filenames in assessment file preview flows. User-supplied filename values are persisted and later rendered into HTML/attribute contexts without output encoding, allowing attacker-controlled JavaScript to execute in the browser of any user who views the affected page. Because the payload is stored server-side and rendered to other users, exploitation is persistent and can impact privileged accounts. This vulnerability is fixed in 1.8.3.
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-44669 has been found in FACTION.
Confidential information can be exposed externally. CVSS score: 8.7/10.
What to do: upgrade FACTION to 1.8.3 or later.
If unsure, ask your IT team or search "FACTION CVE-2026-44669" on the vendor's site.
CVE-2026-44669 (FACTION) — CWE-79 / CVSS v3 8.7
Attack vector: remote (network-reachable)
Patched: 1.8.3 — 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 FACTION.
Check the vendor advisory for the affected versions of FACTION.
Severity: High (CVSS 8.7/10). Confidential information can be exposed externally.
Update to 1.8.3.
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 'FACTION' . 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 'FACTION' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
FACTIONを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade FACTION to 1.8.3ステージング環境で 1.8.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- web github.com