Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2023-45815 medium CVSS 6.4

Cross-Site Scripting (XSS) in archivebox (CVE-2023-45815)

Summary

Cross-site scripting in archivebox (CVE-2023-45815). Confidential information can be exposed externally. Mitigation: upgrade to 0.9.0 or later.

Original description

The description as published by the source.

Related issue & discussion:

Impact

Any users who save untrusted URLs and view the content they output.

The impact is potentially severe if you are logged in to the ArchiveBox admin site in the same browser session and view an archived malicious page designed to target your ArchiveBox instance. Malicious JS could potentially act using your logged-in admin credentials and add/remove/modify snapshots, add/remove/modify ArchiveBox users, and generally do anything an admin user could do.

The impact is less severe for non-logged-in users, as malicious JS cannot modify any archives, but it can still read all the other archived content by fetching the snapshot index and iterating through it.

Because all of ArchiveBox's archived content is served from the same host and port as the admin panel with 0 XSS protections, when archived pages are viewed the JS executes in the same context as all the other archived pages (and the admin panel), defeating most of the browser's usual CORS/CSRF security protections and leading to this issue.

Patches

Follow here for progress on mitigating this issue: https://github.com/ArchiveBox/ArchiveBox/issues/239

Workarounds

Disable the risky extractors by setting [`archivebox config --set SAVE_WGET=False SAVE_DOM=F…

Source: GitHub Security Advisories (Global) 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-2023-45815 has been found in archivebox.
Confidential information can be exposed externally. CVSS score: 6.4/10.
What to do: upgrade archivebox to 0.9.0 or later.
If unsure, ask your IT team or search "archivebox CVE-2023-45815" on the vendor's site.

CVE-2023-45815 (archivebox) — CWE-79 / CVSS v3 6.4
Attack vector: remote (network-reachable)
Patched: 0.9.0 — apply immediately
Workaround: Disable the risky extractors by setting archivebox config --set SAVE_WGET=False SAVE_DOM=False, ensure you are always logged out, or serve only a [static HTML version](https:/
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 archivebox.

📍 Affected scope

Check the vendor advisory for the affected versions of archivebox.

🔥 Severity

Severity: Medium (CVSS 6.4/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 0.9.0.

🛡️ Workaround

Workaround: Disable the risky extractors by setting archivebox config --set SAVE_WGET=False SAVE_DOM=False, ensure you are always logged out, or serve only a [static HTML version](https:/

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'archivebox' . 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

  1. 1
    Identify exposure identify 
    grep -r 'archivebox' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で archivebox を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    Disable the risky extractors by setting [`archivebox config --set SAVE_WGET=False SAVE_DOM=False`](https://github.com/ArchiveBox/ArchiveBox/wiki/Configuration#save_wget), ensure you are always logged out, or serve only a [static HTML version](https:/

    パッチが適用されるまでの応急処置として、Disable the risky extractors by setting archivebox config --set SAVE_WGET=False SAVE_DOM=False, ensure you are always logged out, or serve only a [static HTML version](https:/ を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade archivebox to 0.9.0

    ステージング環境で 0.9.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

pip archivebox
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.9.0"}]}]
PyPI archivebox
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.9.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details