# CVE-2024-23329: changedetection.io API endpoint is not secured with API token

Source: https://junglewise.ai/threats/cve-2024-23329-changedetection-io-api-endpoint-is-not-secured-with-api-token  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2024-01-19  
License: CC BY 4.0 with a link back

CVE-2024-23329 · Severity: low · CVSS 3.1 · Published 2024-01-19

changedetection.io is an open source tool designed to monitor websites for content changes. In affected versions the API endpoint `/api/v1/watch/<uuid>/history` can be accessed by any unauthorized user. As a result any unauthorized user can check one's watch history. However, because unauthorized party first needs to know a watch UUID, and the watch history endpoint itself returns only paths to the snapshot on the server, an impact on users' data privacy is minimal. This issue has been addressed in version 0.45.13. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Technologies: [changedetection.io (PyPI)](https://junglewise.ai/threats/technologies/changedetection-io). Vendors: [PyPI](https://junglewise.ai/threats/vendors/pypi).

## Quick answers

**Is CVE-2024-23329 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2024-23329 being exploited in the wild.

**How severe is CVE-2024-23329?** Low severity, with a CVSS score of 3.1, published 19 January 2024.

**Which products and versions are affected?** changedetection.io (PyPI) ECOSYSTEM:introduced=0.39.14,fixed=0.45.13, GIT:introduced=0,fixed=402f1e47e78ecd155b1e90f30cce424ff7763e0f|ECOSYSTEM:introduced=0.39.14,fixed=0.45.13.

**Is there a fix for CVE-2024-23329?** Yes. changedetection.io (PyPI): upgrade to 0.45.13 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2024-23329?** Check whether you run changedetection.io (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- changedetection.io (PyPI): upgrade to 0.45.13 or later

  ```sh
  pip install "changedetection.io>=0.45.13"
  ```


## Affected products

- changedetection.io (PyPI) ECOSYSTEM:introduced=0.39.14,fixed=0.45.13, GIT:introduced=0,fixed=402f1e47e78ecd155b1e90f30cce424ff7763e0f|ECOSYSTEM:introduced=0.39.14,fixed=0.45.13

## Identifiers

- CVE-2024-23329
- GHSA-hcvp-2cc7-jrwr
- PYSEC-2024-15

## Related threats

- [dgtlmoon changedetection.io path traversal in static content route](https://junglewise.ai/threats/cve-2026-25527-dgtlmoon-changedetection-io-path-traversal-in-static-content)
- [PYSEC-2026-1241 - ChangeDetection.io XSS in watch overview](https://junglewise.ai/threats/cve-2025-52558-changedetection-io-xss-in-watch-overview)
- [PYSEC-2026-1242 - changedetection.io Vulnerable to Improper Input Validation Leading to LFR/Path Traversal](https://junglewise.ai/threats/cve-2024-56509-changedetection-io-vulnerable-to-improper-input-validation)
- [PYSEC-2026-1239 - changedetection.io path traversal using file URI scheme without supplying hostname](https://junglewise.ai/threats/cve-2024-51998-changedetection-io-path-traversal-using-file-uri-scheme-without)
- [PYSEC-2026-1240 - changedetection.io Path Traversal](https://junglewise.ai/threats/cve-2024-51483-changedetection-io-path-traversal)