<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-04T08:37:43.697774+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-201140</id>
    <title>EUVD-2026-201140</title>
    <updated>2026-10-04T08:37:43.903515+00:00</updated>
    <content>EUVD-2026-201140</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-201140"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2024-23329</id>
    <title>fkie_cve-2024-23329</title>
    <updated>2026-10-04T08:37:43.903556+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>changedetection.io is an open source tool designed to monitor websites for content changes. In affected versions the API endpoint `/api/v1/watch/&lt;uuid&gt;/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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2024-23329"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-hcvp-2cc7-jrwr</id>
    <title>GHSA-hcvp-2cc7-jrwr — changedetection.io API endpoint is not secured with API token</title>
    <updated>2026-10-04T08:37:43.903594+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: changedetection.io</p>
<p>### Summary</p>
<p>API endpoint `/api/v1/watch/&lt;uuid&gt;/history` can be accessed by any unauthorized user.</p>
<p>### Details</p>
<p>WatchHistory resource does not have `@auth.check_token` annotation, which means it can be accessed without providing `x-api-key` header.</p>
<p>https://github.com/dgtlmoon/changedetection.io/blob/9510345e01ea8e308c339163d8e8b030ce5ac7f1/changedetectionio/api/api_v1.py#L129-L156</p>
<p>### PoC</p>
<p>1. Get list of watch with `x-api-key`:
```sh
$ curl -H "x-api-key: apikeyhere" http://localhost:5000/api/v1/watch
{"uuid": ...}
```
2. Call for history of snapshots without `x-api-key`. Expected - 401/403 error. Actual - list of snapshots is listed.
```sh
$ curl http://localhost:5000/api/v1/watch/uuid/history
{"timestamp": "/path/to/snapshot.txt"}
```</p>
<p>### Impact</p>
<p>Anybody can check one's watch history. However, because unauthorized party first needs to know 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.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-hcvp-2cc7-jrwr"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2024-23329</id>
    <title>gsd-2024-23329</title>
    <updated>2026-10-04T08:37:43.903634+00:00</updated>
    <content>gsd-2024-23329</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2024-23329"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/pysec-2024-15</id>
    <title>PYSEC-2024-15</title>
    <updated>2026-10-04T08:37:43.903648+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: changedetection-io</p>
<p>changedetection.io is an open source tool designed to monitor websites for content changes. In affected versions the API endpoint `/api/v1/watch/&lt;uuid&gt;/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.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/pysec-2024-15"/>
  </entry>
</feed>
