Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.4amended

Viewing wget extractor output while logged in as an admin allows archived JS to execute in the admins context

CVE-2023-45815GHSA-cr45-98w9-gwqx

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (archivebox 0.9.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
7.4 · CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2023-45815: 0.81% estimated exploitation activity in the next 30 days; percentile 56.95 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Related issue & discussion: - https://github.com/ArchiveBox/ArchiveBox/issues/239 - https://github.com/ArchiveBox/ArchiveBox/wiki/Security-Overview#publishing - https://github.com/ArchiveBox/ArchiveBox/wiki/Publishing-Your-Archive#security-concerns 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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-cr45-98w9-gwqx

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-cr45-98w9-gwqx

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-45815

Advisory: Viewing wget extractor output while logged in as an admin allows archived JS to execute in the admins context
IDs: CVE-2023-45815, GHSA-cr45-98w9-gwqx
Record: https://patchnext.com/advisories/cve-2023-45815 (revision 3, source checked 26 Oct 2026, 13:46 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: archivebox 0.9.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI archivebox: affected < 0.9.0; fixed in 0.9.0

## Suggested inspection (read-only)
- `python -m pip show archivebox`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on archivebox.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-cr45-98w9-gwqx (OSV record GHSA-cr45-98w9-gwqx lists affected ranges: PyPI archivebox >=0 <0.9.0 (fixed))
- Verified: https://github.com/advisories/GHSA-cr45-98w9-gwqx (GitHub-reviewed advisory GHSA-cr45-98w9-gwqx lists affected ranges: PyPI archivebox >=0 <0.9.0)

Commands are suggestions: review each one before running it.

Loading voting…