---
title: >-
  Protection from CVE-2025-64459 (Django SQL injection via _connector or
  _negated)
summary: null
url: >-
  https://www.fastly.com/documentation/reference/changes/2025/11/protection-from-cve-2025-64459-django-sql-injection
---

A SQL injection vulnerability has been found in Django and has been assigned CVE-2025-64459. Fastly has created a virtual patch for it that is now available within your account. To activate it and add protection to your services, follow the steps for your control panel below.

## Next-Gen WAF control panel

### Professional or Premier platform

1.   Log in to the [Next-Gen WAF control panel](https://dashboard.signalsciences.net).

2.   From the **Sites** menu, select a site if you have more than one site.

3. From the **Rules** menu, select **Templated Rules**.
4. In the search bar, enter `CVE-2025-64459` and then click **View** for the CVE-2025-64459 templated rule.
5. Click **Configure** and then **Add trigger**.
6. Select the **Block requests from an IP immediately if the CVE-2025-64459 signal is observed** checkbox.
7. Click **Update rule**.

### Essential platform

1.   Log in to the [Next-Gen WAF control panel](https://dashboard.signalsciences.net).

2.   From the **Sites** menu, select a site if you have more than one site.

3. Click the **Signals** tab.
4. In the search bar, enter `CVE-2025-64459` and then click **View** for the CVE-2025-64459 tag.
5. Click the **Detections** tab and then **Add detection**.
6. Verify the switch is set to **Enabled**.
7. Click **Create detection**.
8. Click the **Alerts** tab and then **Add alert**.
9. In the **Status** area, set the switch to **Enabled**.
10. Click **Save alert**.

## Fastly control panel

1.   Log in to the [Fastly control panel](https://manage.fastly.com).

2.   Go to **Security** > **Next-Gen WAF** > [**Workspaces**](https://manage.fastly.com/security/ngwaf/workspaces).

3. Click **Virtual Patches**.
4. In the search bar, enter `CVE-2025-64459` and then click the pencil to the right of the CVE-2025-64459 virtual patch.
5. From the **Status** menu, select **Enabled**.
6. _(Optional)_ If your workspace is in blocking mode, choose whether to **Block requests** or **Log requests** if the CVE-2025-64459 signal is observed.
7. Click **Update virtual patch**.