Is CVE-2026-34747 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-34747 being exploited in the wild.

How severe is CVE-2026-34747?

High severity, with a CVSS score of 8.5, published 1 April 2026.

Which products and versions are affected?

payload (npm) SEMVER:introduced=0,fixed=3.79.1.

Is there a fix for CVE-2026-34747?

Yes. payload (npm): upgrade to 3.79.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-34747 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-34747?

Check whether you run payload (npm) or PayloadCMS Payload at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-34747: Payload SQL Injection via Query Handling

CVE-2026-34747 · Severity: high · CVSS 8.5 · Published 2026-04-01

Payload is a popular open-source CMS and backend framework that handles dynamic database queries. An SQL injection vulnerability in its query input validation allows authenticated attackers to craft malicious requests that can read, modify, or delete data from collections. This could expose sensitive customer data or compromise the integrity of business-critical information stored in the database.

Technologies: payload (npm), PayloadCMS Payload. Vendors: npm, PayloadCMS.

Quick answers

Is CVE-2026-34747 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-34747 being exploited in the wild.
How severe is CVE-2026-34747?: High severity, with a CVSS score of 8.5, published 1 April 2026.
Which products and versions are affected?: payload (npm) SEMVER:introduced=0,fixed=3.79.1.
Is there a fix for CVE-2026-34747?: Yes. payload (npm): upgrade to 3.79.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-34747 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-34747?: Check whether you run payload (npm) or PayloadCMS Payload at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

payload (npm): upgrade to 3.79.1 or later
```
npm install payload@3.79.1
```

Technical details

The vulnerability is an SQL injection (CWE-89) caused by insufficient validation of request inputs used in query handling. An attacker with authentication credentials can craft requests with specially-crafted query parameters to inject arbitrary SQL commands into the query execution path, potentially reading or modifying data in collections. The attack vector is network-accessible with low attack complexity; authentication is required (PR:L). The fix involves hardening query input validation and is available in Payload v3.79.1 and later. Workarounds include restricting access to affected endpoints to trusted users only and implementing client-side input validation.

Affected products

Payload Payload < 3.79.1

Identifiers

CVE-2026-34747
GHSA-7xxh-373w-35vg

Timeline

2026-04-01: disclosed: Published in GitHub Advisory Database
2026-04-01: patched: Fixed in v3.79.1

References

https://github.com/payloadcms/payload/security/advisories/GHSA-7xxh-373w-35vg

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.