Skip to main content
VulnerabilityPublished

CVE-2026-34590: gitroomhq postiz-app · Server-Side Request Forgery (SSRF)

Affects gitroomhq postiz-appSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.4 Medium : upgrade to 2.21.4 when convenient.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.21.4
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade postiz-app and gitroomhq/postiz-app to 2.21.4.

Affected software

ProductAffectedFixed in
gitroomhqpostiz-appAffected
  • <2.21.4
Fixed in
  • 2.21.4
GitHubgitroomhq/postiz-apppkg:github/gitroomhq/postiz-appOther threatsAffected
  • <2.21.4
Fixed in
  • 2.21.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

This vulnerability is patched in postiz-app version 2.21.4. Users should upgrade to version 2.21.4 or later to ensure the @IsSafeWebhookUrl validator is applied on the webhook creation endpoint. No additional mitigation is required once the update is applied.

Description

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.

References

Community reviews

Loading reviews…