PYSEC-2026-1239
Vulnerability from pysec - Published: 2026-07-07 14:34 - Updated: 2026-07-07 17:23Summary
The validation for the file URI scheme falls short, and results in an attacker being able to read any file on the system. This issue only affects instances with a webdriver enabled, and ALLOW_FILE_URI false or not defined.
Details
The check used for URL protocol, is_safe_url, allows file: as a URL scheme:
https://github.com/dgtlmoon/changedetection.io/blob/e0abf0b50507a8a3d0c1d8522ab23519b3e4cdf4/changedetectionio/model/Watch.py#L11-L13
It later checks if local files are permitted, but one of the preconditions for the check is that the URL starts with file://. The issue comes with the fact that the file URI scheme is not required to have double slashes.
A valid file URI must therefore begin with either
file:/path(no hostname),file:///path(empty hostname), orfile://hostname/path. — Wikipedia
https://github.com/dgtlmoon/changedetection.io/blob/e0abf0b50507a8a3d0c1d8522ab23519b3e4cdf4/changedetectionio/processors/init.py#L37-L41
PoC
- Open up a changedetection.io instance with a webdriver configured
- Create a new watch:
file:/etc/passwdor a similar path for your operating system. Enable webdriver mode - Wait for it to be checked
- Open preview
- Notice contents of the file
| Name | purl | changedetection-io | pkg:pypi/changedetection-io |
|---|
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "changedetection-io",
"purl": "pkg:pypi/changedetection-io"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.47.6"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.38.2",
"0.39",
"0.39.1",
"0.39.10",
"0.39.10.post1",
"0.39.10.post2",
"0.39.11",
"0.39.12",
"0.39.13",
"0.39.13.1",
"0.39.14",
"0.39.14.1",
"0.39.15",
"0.39.16",
"0.39.17",
"0.39.17.1",
"0.39.17.2",
"0.39.18",
"0.39.19",
"0.39.19.1",
"0.39.2",
"0.39.20",
"0.39.20.1",
"0.39.20.2",
"0.39.20.3",
"0.39.20.4",
"0.39.21",
"0.39.21.1",
"0.39.22",
"0.39.22.1",
"0.39.3",
"0.39.4",
"0.39.5",
"0.39.6",
"0.39.7",
"0.39.8",
"0.39.9",
"0.40.0",
"0.40.0.1",
"0.40.0.2",
"0.40.0.3",
"0.40.0.4",
"0.40.1.0",
"0.40.1.1",
"0.40.2",
"0.40.3",
"0.41",
"0.41.1",
"0.42",
"0.42.1",
"0.42.2",
"0.42.3",
"0.43.1",
"0.43.2",
"0.44",
"0.44.1",
"0.45",
"0.45.1",
"0.45.11",
"0.45.12",
"0.45.13",
"0.45.14",
"0.45.15",
"0.45.16",
"0.45.17",
"0.45.18",
"0.45.19",
"0.45.2",
"0.45.20",
"0.45.21",
"0.45.22",
"0.45.23",
"0.45.24",
"0.45.25",
"0.45.26",
"0.45.3",
"0.45.4",
"0.45.5",
"0.45.6",
"0.45.7",
"0.45.7.1",
"0.45.7.2",
"0.45.7.3",
"0.45.8",
"0.45.8.1",
"0.45.9",
"0.46.0",
"0.46.1",
"0.46.2",
"0.46.3",
"0.46.4",
"0.47.0",
"0.47.1",
"0.47.2",
"0.47.3",
"0.47.4",
"0.47.5"
]
}
],
"aliases": [
"CVE-2024-51998",
"GHSA-6jrf-rcjf-245r"
],
"details": "### Summary\n\nThe validation for the file URI scheme falls short, and results in an attacker being able to read any file on the system. This issue only affects instances with a webdriver enabled, and `ALLOW_FILE_URI` false or not defined.\n\n### Details\n\nThe check used for URL protocol, `is_safe_url`, allows `file:` as a URL scheme:\n\nhttps://github.com/dgtlmoon/changedetection.io/blob/e0abf0b50507a8a3d0c1d8522ab23519b3e4cdf4/changedetectionio/model/Watch.py#L11-L13\n\nIt later checks if local files are permitted, but one of the preconditions for the check is that the URL starts with `file://`. The issue comes with the fact that the file URI scheme is not required to have double slashes.\n\n\u003e A valid file URI must therefore begin with either `file:/path` (no hostname), `file:///path` (empty hostname), or `file://hostname/path`.\n\u003e \u2014 [Wikipedia](https://en.wikipedia.org/wiki/File_URI_scheme#Number_of_slash_characters)\n\nhttps://github.com/dgtlmoon/changedetection.io/blob/e0abf0b50507a8a3d0c1d8522ab23519b3e4cdf4/changedetectionio/processors/__init__.py#L37-L41\n\n### PoC\n\n1. Open up a changedetection.io instance with a webdriver configured\n2. Create a new watch: `file:/etc/passwd` or a similar path for your operating system. Enable webdriver mode\n3. Wait for it to be checked\n4. Open preview\n5. Notice contents of the file\n",
"id": "PYSEC-2026-1239",
"modified": "2026-07-07T17:23:53.733475Z",
"published": "2026-07-07T14:34:44.117909Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/dgtlmoon/changedetection.io/security/advisories/GHSA-6jrf-rcjf-245r"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-51998"
},
{
"type": "WEB",
"url": "https://github.com/dgtlmoon/changedetection.io/commit/49bc982c697169c98b79698889fb9d26f6b3317f"
},
{
"type": "PACKAGE",
"url": "https://github.com/dgtlmoon/changedetection.io"
},
{
"type": "WEB",
"url": "https://github.com/dgtlmoon/changedetection.io/blob/e0abf0b50507a8a3d0c1d8522ab23519b3e4cdf4/changedetectionio/model/Watch.py#L11-L13"
},
{
"type": "WEB",
"url": "https://github.com/dgtlmoon/changedetection.io/blob/e0abf0b50507a8a3d0c1d8522ab23519b3e4cdf4/changedetectionio/processors/__init__.py#L37-L41"
},
{
"type": "WEB",
"url": "https://github.com/dgtlmoon/changedetection.io/releases/tag/0.47.06"
},
{
"type": "PACKAGE",
"url": "https://pypi.org/project/changedetection-io"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-6jrf-rcjf-245r"
}
],
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "changedetection.io path traversal using file URI scheme without supplying hostname"
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.