Answer in brief
CVE-2026-58200 records a High severity (CVSS 7.1) vulnerability in @jhb.software/payload-cloudinary-plugin: Arbitrary Cloudinary API Parameter Signing. The current sources do not mark it as known exploited. The current feed maps jhb-software/payload-plugins (generic), @jhb.software/payload-cloudinary-plugin (npm), @jhb.software/payload-cloudinary-plugin (npm). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps jhb-software/payload-plugins (generic), @jhb.software/payload-cloudinary-plugin (npm), @jhb.software/payload-cloudinary-plugin (npm). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| jhb-software/payload-pluginsgeneric | >=0.3.0 <0.4.0 | 0.4.0 |
| @jhb.software/payload-cloudinary-pluginnpm | >=0.3.0,<0.4.0 | 0.4.0 |
| @jhb.software/payload-cloudinary-pluginnpm | >=0.3.0 <0.4.0 | 0.4.0 |
Published upstream
Sep 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 19, 2026
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.
Quoted source text, attributed separately from HOL analysis.