# CVE-2026-58200: @jhb.software/payload-cloudinary-plugin: Arbitrary Cloudinary API Parameter Signing

> Authenticated users can generate valid Cloudinary signatures for unauthorized parameters, allowing asset replacement and unauthorized uploads when clientUploads is enabled.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** GHSA-h5x8-xp6m-x6q4

## What is CVE-2026-58200?

CVE-2026-58200 is a high-severity missing authorization vulnerability in jhb-software payload-plugins, published on 15 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Payload Plugins is a collection of plugins designed to enhance Payload CMS. From 0.3.0 until 0.4.0, @jhb.software/payload-cloudinary-plugin deployments with clientUploads enabled expose POST /api/cloudinary-generate-signature, whose handler in cloudinary/src/getGenerateSignature.ts passes attacker-controlled body.paramsToSign directly to cloudinary.utils.api_sign_request without a key allowlist, collection policy, timestamp freshness check, or configured-folder enforcement. Any authenticated Payload user can obtain a valid Cloudinary HMAC-SHA1 signature for unauthorized parameters such as overwrite, type, notification_url, invalidate, folder, and public_id. The signature can authorize asset replacement, upload visibility changes, callbacks to attacker-selected URLs, cache invalidation, and uploads outside the intended folder. The client-visible Cloudinary API key is expected by the upload design, but the unrestricted server-side signature supplies the authorization value needed to complete these operations. This vulnerability is fixed in 0.4.0.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

## Which versions are affected by CVE-2026-58200?

2 open source packages ship an affected version, including @jhb.software/payload-cloudinary-plugin.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@jhb.software/payload-cloudinary-plugin` | npm | From 0.3.0 | 0.4.0 |
| `@jhb.software/payload-cloudinary-plugin` | npm | From 0.3.0 | 0.4.0 |

## How do I fix CVE-2026-58200?

Upgrade @jhb.software/payload-cloudinary-plugin to 0.4.0 or later.

## Is CVE-2026-58200 being exploited?

There is no known exploitation of CVE-2026-58200 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-58200 and fix it if it is affected.

What it is: CVE-2026-58200 is a high-severity missing authorization vulnerability in jhb-software payload-plugins, published on 15 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-58200 in the wild and no public exploit code.

Affected packages and fixed versions:
- @jhb.software/payload-cloudinary-plugin (npm): affected from 0.3.0; fixed in 0.4.0
- @jhb.software/payload-cloudinary-plugin (npm): affected from 0.3.0; fixed in 0.4.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-58200/ (Markdown: https://insights.sbomify.com/CVE-2026-58200/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-58200
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-58200
- OSV: https://osv.dev/vulnerability/CVE-2026-58200

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-58200/
Summaries are generated and may contain mistakes; the official description above is the record.