{"answers":{"affected":"2 open source packages ship an affected version, including @jhb.software/payload-cloudinary-plugin.","exploited":"There is no known exploitation of CVE-2026-58200 in the wild and no public exploit code.","fix":"Upgrade @jhb.software/payload-cloudinary-plugin to 0.4.0 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-58200 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-58200 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @jhb.software/payload-cloudinary-plugin (npm): affected from 0.3.0; fixed in 0.4.0\n- @jhb.software/payload-cloudinary-plugin (npm): affected from 0.3.0; fixed in 0.4.0\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-58200/ (Markdown: https://insights.sbomify.com/CVE-2026-58200/index.md)","id":"CVE-2026-58200","markdown":"https://insights.sbomify.com/CVE-2026-58200/index.md","name":"CVE-2026-58200","record":{"aliases":["GHSA-h5x8-xp6m-x6q4"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Payload CMS plugin","requires_auth":"low_privilege","summary":"Authenticated users can generate valid Cloudinary signatures for unauthorized parameters, allowing asset replacement and unauthorized uploads when clientUploads is enabled.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"@jhb.software/payload-cloudinary-plugin: Arbitrary Cloudinary API Parameter Signing","id":"CVE-2026-58200","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"Lokka: Azure Resource Manager URL path validation issue","id":"CVE-2026-58201"},"packages":[{"ecosystem":"npm","fixed":["0.4.0"],"introduced":["0.3.0"],"last_affected":[],"package":"@jhb.software/payload-cloudinary-plugin","purl":null,"source":"GHSA-h5x8-xp6m-x6q4"},{"ecosystem":"npm","fixed":["0.4.0"],"introduced":["0.3.0"],"last_affected":[],"package":"@jhb.software/payload-cloudinary-plugin","purl":"pkg:npm/%40jhb.software/payload-cloudinary-plugin","source":"GHSA-h5x8-xp6m-x6q4"}],"prev":{"headline":"ChatterBot: Symlink-Following Arbitrary Write via UbuntuCorpusTrainer","id":"CVE-2026-58198"},"products":["payload-plugins"],"published":"2026-09-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-15","vendors":["jhb-software"]},"summary":"Authenticated users can generate valid Cloudinary signatures for unauthorized parameters, allowing asset replacement and unauthorized uploads when clientUploads is enabled.","url":"https://insights.sbomify.com/CVE-2026-58200/"}