Vulnerability in Payload Plugins (CVE-2026-58200)
Summary
Vulnerability in Payload Plugins (CVE-2026-58200). Data can be tampered with by attackers. Exploitable via POST /api/cloudinary-generate-signature. Mitigation: upgrade to 0.4.0 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-58200 has been found in Payload Plugins.
Attackers can target a specific entry point like POST /api/cloudinary-generate-signature over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.1/10.
What to do: upgrade Payload Plugins to 0.4.0 or later.
If unsure, ask your IT team or search "Payload Plugins CVE-2026-58200" on the vendor's site.
CVE-2026-58200 (Payload Plugins) — CWE-347 / CVSS v3 7.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/cloudinary-generate-signature
Patched: 0.4.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-347) exists in Payload Plugins. Attackers reach the vulnerable code path via POST /api/cloudinary-generate-signature.
Check the vendor advisory for the affected versions of Payload Plugins. Attack surface: POST /api/cloudinary-generate-signature.
Severity: High (CVSS 7.1/10). Data can be tampered with by attackers.
Update to 0.4.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /api/cloudinary-generate-signature requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Payload Plugins を使っているサービスとバージョンを洗い出す。
-
2Hunt for indicators of compromise detect
grep 'POST /api/cloudinary-generate-signature' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/cloudinary-generate-signatureへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade Payload Plugins to 0.4.0ステージング環境で 0.4.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /api/cloudinary-generate-signature on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。