# CVE-2024-56509: changedetection.io has Improper Input Validation Leading to LFR/Path Traversal

> Attackers can exploit improper input validation to perform local file read or path traversal attacks, accessing sensitive files on the server.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Dec 2024
- **Updated:** 27 Dec 2024
- **Also known as:** GHSA-j5vv-6wjg-cfr8, PYSEC-2026-1242

## What is CVE-2024-56509?

CVE-2024-56509 is a high-severity path traversal vulnerability in dgtlmoon changedetection.io, published on 27 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

changedetection.io is a free open source web page change detection, website watcher, restock monitor and notification service. Improper input validation in the application can allow attackers to perform local file read (LFR) or path traversal attacks. These vulnerabilities occur when user input is used to construct file paths without adequate sanitization or validation. For example, using file:../../../etc/passwd or file: ///etc/passwd can bypass weak validations and allow unauthorized access to sensitive files. Even though this has been addressed in previous patch, it is still insufficient. This vulnerability is fixed in 0.48.05.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2024-56509?

3 open source packages ship an affected version, including changedetection.io and changedetection-io.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `changedetection.io` | PyPI | All versions | 0.48.05 |
| `changedetection-io` | PyPI | All versions | 0.48.05 |
| `changedetection-io` | PyPI | All versions | 0.48.05 |

## How do I fix CVE-2024-56509?

Upgrade changedetection.io to 0.48.05 or later.

## Is CVE-2024-56509 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-56509 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-56509 and fix it if it is affected.

What it is: CVE-2024-56509 is a high-severity path traversal vulnerability in dgtlmoon changedetection.io, published on 27 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-56509 exists.

Affected packages and fixed versions:
- changedetection.io (PyPI): affected all versions; fixed in 0.48.05
- changedetection-io (PyPI): affected all versions; fixed in 0.48.05
- changedetection-io (PyPI): affected all versions; fixed in 0.48.05

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-2024-56509/ (Markdown: https://insights.sbomify.com/CVE-2024-56509/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-56509
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-56509
- OSV: https://osv.dev/vulnerability/CVE-2024-56509

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-56509/
Summaries are generated and may contain mistakes; the official description above is the record.