Skip to main content
Menu
CVEs

CVE

Livewire PowerGrid: SQL Injection through the public `sortDirection` Livewire property in the `naturalSort` order-by path

Livewire PowerGrid versions 6.0.0 up to but not including 6.10.4 are affected when a table uses a naturalSort column. The fix is in 6.10.4.

CVE-2026-65971

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

7.6HighCNA
Exploited
No known exploitation
Fix
Fixed in 6.10.4
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Livewire PowerGrid versions from 6.0.0 up to but not including 6.10.4 A PowerGrid table that uses a naturalSort column

Published
Last modified
Reference
Last checked
16/100 · provisional
Specific setups only
1 proof of concept on GitHub

Summary

Livewire PowerGrid, a data table package for Laravel Livewire, is affected by an SQL injection flaw in its sorting code. A remote attacker with a low-privilege account can send a crafted request to the Livewire update endpoint to run arbitrary SQL against the database.

Read the original description

Livewire PowerGrid creates data tables based on Laravel Livewire library. From version 6.0.0 to before version 6.10.4, the public Livewire property sortDirection is interpolated verbatim into a raw SQL ORDER BY clause and is not restricted to asc/desc, allowing arbitrary SQL injection through POST /livewire/update. This issue has been patched in version 6.10.4.

Who should check

Anyone running Power-Components livewire-powergrid from 6.0.0 before 6.10.4 with a table using naturalSort columns

Read the source excerpt

“>= 6.0.0, < 6.10.4”

github.com

cve.now Index

16Pcve.now Index 16 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.6/10CVSS 7.6
  • No patch0/5No signal

What would change the score

  • Would score about 66 if added to CISA KEV
  • Would score about 61 if CISA's SSVC rates exploitation active
  • Would score about 23 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Livewire PowerGrid versions from 6.0.0 up to but not including 6.10.4 A PowerGrid table that uses a naturalSort column
  • Upgrade to a fixed version: 6.10.4.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-65971 (Livewire PowerGrid: SQL Injection through the public `sortDirection` Livewire property in the `naturalSort` order-by path), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-65971 (entry last updated 2026-11-11):
Affected:
- Power-Components livewire-powergrid: from 6.0.0, fixed in 6.10.4
Fixed versions: 6.10.4.
Conditions (all must be true for the bug to be hit):
- Livewire PowerGrid versions from 6.0.0 up to but not including 6.10.4 (source: https://github.com/Power-Components/livewire-powergrid/security/advisories/GHSA-7fgc-3h6c-698r)
- A PowerGrid table that uses a naturalSort column (source: https://github.com/Power-Components/livewire-powergrid/security/advisories/GHSA-7fgc-3h6c-698r)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-65971 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-65971 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/Power-Components/livewire-powergrid/security/advisories/GHSA-7fgc-3h6c-698r
- https://github.com/Power-Components/livewire-powergrid/commit/13d047bf1637e82926e6914aa3ca0f29a4c9704a
- https://github.com/Power-Components/livewire-powergrid/releases/tag/v6.10.4
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-65971
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-65971"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • Power-Components livewire-powergrid

    From 6.0.0 · fixed in 6.10.4

Evidence 6

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Public exploit code · 1

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

  1. Exploit

Other links · 2

  1. Repository
  2. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-65971

Is CVE-2026-65971 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

The public sortDirection Livewire property reaches the naturalSort order-by query without proper protection, which allows SQL injection. The advisory says this can read arbitrary database data, including other tables, password hashes and tokens.Source: github.com, github.com

Which versions are affected by CVE-2026-65971?

livewire-powergrid: from 6.0.0 before 6.10.4.Source: cve.now feed data

Am I affected, and how do I check?

Livewire PowerGrid versions from 6.0.0 up to but not including 6.10.4 are in scope. The bug requires a PowerGrid table that uses a naturalSort column, so check the installed package version and whether any table defines a naturalSort column.Source: github.com, github.com

How do I fix CVE-2026-65971?

Upgrade livewire-powergrid to 6.10.4, the version the advisory lists as the fix. No workaround is given in the checked facts.Source: github.com, github.com