Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 10.0amended

changedetection.io has a Server Side Template Injection using Jinja2 which allows Remote Command Execution

CVE-2024-32651GHSA-4r7v-whpg-8rx3

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (changedetection-io 0.45.21), 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
10.0 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
EPSS
  • CVE-2024-32651: 85.26% estimated exploitation activity in the next 30 days; percentile 99.72 (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.

Summary A Server Side Template Injection in changedetection.io caused by usage of unsafe functions of Jinja2 allows Remote Command Execution on the server host.

Details changedetection.io version: 0.45.20 ``` docker images REPOSITORY TAG IMAGE ID CREATED SIZE dgtlmoon/changedetection.io latest 53529c2e69f1 44 hours ago 423MB ``` The vulnerability is caused by the usage of vulnerable functions of Jinja2 template engine. ```python from jinja2 import Environment, BaseLoader ...

Get the notification body from datastore jinja2_env = Environment(loader=BaseLoader) n_body = jinja2_env.from_string(n_object.get('notification_body', '')).render(notification_parameters) n_title = jinja2_env.from_string(n_object.get('notification_title', '')).render(notification_parameters) ```

PoC 1. Create/Edit a URL watch item 2. Under *Notifications* tab insert this payload: ```python {{ self.init.globals.builtins.import('os').popen('id').read() }} ``` !Screenshot from…

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

    Amended from osv record GHSA-4r7v-whpg-8rx3

  2. Revision 3 · amended ·

    Amended from ghsa record GHSA-4r7v-whpg-8rx3

  3. Revision 2 · amended ·

    Amended from ghsa record GHSA-4r7v-whpg-8rx3

  4. Revision 1 · created ·

    Published from osv record GHSA-4r7v-whpg-8rx3

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-2024-32651

Advisory: changedetection.io has a Server Side Template Injection using Jinja2 which allows Remote Command Execution
IDs: CVE-2024-32651, GHSA-4r7v-whpg-8rx3
Record: https://patchnext.com/advisories/cve-2024-32651 (revision 4, source checked 28 Oct 2026, 06:10 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 10.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: changedetection-io 0.45.21. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI changedetection-io: affected < 0.45.21; fixed in 0.45.21

## Suggested inspection (read-only)
- `python -m pip show changedetection-io`: 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 changedetection-io.
- 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-4r7v-whpg-8rx3 (OSV record GHSA-4r7v-whpg-8rx3 lists affected ranges: PyPI changedetection-io >=0 <0.45.21 (fixed))
- Verified: https://github.com/advisories/GHSA-4r7v-whpg-8rx3 (GitHub-reviewed advisory GHSA-4r7v-whpg-8rx3 lists affected ranges: PyPI changedetection-io >=0 <=0.45.20)

Commands are suggestions: review each one before running it.

Loading voting…