# CVE-2023-45815: Viewing wget extractor output while logged in as an admin allows archived JS to execute in the admins context > Admins viewing archived pages with the wget extractor enabled risk malicious JavaScript executing with admin privileges, allowing full system compromise. - **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 19 Oct 2023 - **Updated:** 7 Jul 2026 - **Also known as:** GHSA-cr45-98w9-gwqx, PYSEC-2023-229 ## What is CVE-2023-45815? CVE-2023-45815 is a medium-severity cross-site scripting vulnerability in ArchiveBox, published on 19 Oct 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. ### Official description ArchiveBox is an open source self-hosted web archiving system. Any users who are using the `wget` extractor and view the content it outputs. 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 Javascript 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 Javascript 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, 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. Version 0.9.0 contains a patch. As a mitigation for this issue would be to disable the wget extractor by setting `archivebox config --set SAVE_WGET=False`, ensure you are always logged out, or serve only a [static HTML version](https://github.com/ArchiveBox/ArchiveBox/wiki/Publishing-Your-Archive#2-export-and-host-it-as-static-html) of your archive. Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2023-45815? 3 open source packages ship an affected version, including archivebox. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `archivebox` | PyPI | All versions | 0.7.0 | | `archivebox` | PyPI | All versions | 0.9.0 | | `archivebox` | PyPI | All versions | 0.9.0 | Products: Archivebox Archivebox. ## How do I fix CVE-2023-45815? Upgrade archivebox to a fixed version for your release line: 0.7.0 or 0.9.0. ## Is CVE-2023-45815 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-45815 exists. ## Other vulnerabilities in ArchiveBox - [CVE-2026-42601](https://insights.sbomify.com/CVE-2026-42601/): ArchiveBox Vulnerable to RCE via unvalidated per-crawl config overrides in AddView (critical 9.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-45815 and fix it if it is affected. What it is: CVE-2023-45815 is a medium-severity cross-site scripting vulnerability in ArchiveBox, published on 19 Oct 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-45815 exists. Affected packages and fixed versions: - archivebox (PyPI): affected all versions; fixed in 0.7.0 - archivebox (PyPI): affected all versions; fixed in 0.9.0 - archivebox (PyPI): affected all versions; fixed in 0.9.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2023-45815/ (Markdown: https://insights.sbomify.com/CVE-2023-45815/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-45815 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-45815 - OSV: https://osv.dev/vulnerability/CVE-2023-45815 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-45815/ Summaries are generated and may contain mistakes; the official description above is the record.