CVE-2026-34590 json
Postiz: SSRF via Webhook Creation Endpoint Missing URL Safety Validation
published 2026-04-02 7 mo ago modified 2026-07-24 3 mo ago also EUVD-2026-18452
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 14%
- public exploits
- 0
- none known
Summary
Postiz is an AI social media scheduling tool. Prior to version 2.21.4, the POST /webhooks/ endpoint for creating webhooks uses WebhooksDto which validates the url field with only @IsUrl() (format check), missing the @IsSafeWebhookUrl validator that blocks internal/private network addresses. The update (PUT /webhooks/) and test (POST /webhooks/send) endpoints correctly apply @IsSafeWebhookUrl. When a post is published, the orchestrator fetches the stored webhook URL without runtime validation, enabling blind SSRF against internal services. This issue has been patched in version 2.21.4.
Patch / fix
- gitroom postiz 2.21.4
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 7 mo ago
Exploit prediction
0.23% chance of exploitation in the next 30 days, higher than 14% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/gitroomhq/postiz-app/security/advisories/GHSA-wc9c-7cv8-m225 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N |
Affected products
- gitroomhq postiz-app
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
References
-
github.com
/gitroomhq/postiz-app/commit/5ae4c950db6aa516a31454b7a45b9480bca40a11
patch
-
github.com
/gitroomhq/postiz-app/security/advisories/GHSA-wc9c-7cv8-m225
exploit, mitigation, vendor-advisory
-
github.com
/gitroomhq/postiz-app/releases/tag/v2.21.4
product, release-notes
Sources
- CVE List CVE-2026-34590
- NVD CVE-2026-34590
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.