# Postiz: forged signed tokens and post-media path traversal let any registered user take over orgs and read server files (CVE-2026-115933, CVE-2026-115932) · pwn.watch

> Two critical bugs in the self-hosted Postiz social media scheduler, both reported with working PoCs by Anthropic. Postiz signed session, invite and password-reset tokens with one shared secret and no purpose marker, and an extension-refresh route signed request data, so any registered user could forge tokens and become super admin of another organization (CVE-2026-115933, CVSS 9.9). A separate path traversal in post media let a registered user have the worker send any server file, including the JWT secret and env file, to their own Discord server (CVE-2026-115932, CVSS 9.6). Both are fixed in Postiz 2.25.3; self-registration is open by default, so upgrade now.

Page: https://pwn.watch/i/postiz-account-takeover-file-read-cve-2026-115933 · generated 2026-10-24T15:42:16.615Z

## Status
- Severity: critical · status: live · patch: patched
- Product: Postiz (gitroomhq/postiz-app), self-hosted
- Started: 2026-10-24
- CVEs: CVE-2026-115933, CVE-2026-115932
- Affected: postiz-app 2.15.0 to before 2.25.3 (CVE-2026-115933, forged tokens); postiz-app 2.23.0 to before 2.25.3 (CVE-2026-115932, path traversal; main route needs the Discord provider configured)
- Fixed in: postiz-app 2.25.3

## Follow this incident
- RSS (one item per update): https://pwn.watch/i/postiz-account-takeover-file-read-cve-2026-115933/feed.xml
- JSON Feed: https://pwn.watch/i/postiz-account-takeover-file-read-cve-2026-115933/feed.json
- Full data (timeline, sources, posts, agentBrief): https://pwn.watch/i/postiz-account-takeover-file-read-cve-2026-115933.json
- This file: https://pwn.watch/i/postiz-account-takeover-file-read-cve-2026-115933/llms.txt

## Updates (newest first)
- 2026-10-24: Postiz 2.25.3 ships fixes for PSA-2026-E9AHFV (CVE-2026-115932, path traversal) and PSA-2026-YT2HMH (CVE-2026-115933, forged tokens); all users are told to upgrade immediately. Workarounds until then: set DISABLE_REGISTRATION=true and block POST /integrations/extension-refresh at the reverse proxy. (https://github.com/gitroomhq/postiz-app/releases/tag/v2.25.3)
- 2026-10-23: Anthropic reports both bugs to Postiz with working PoCs (17:45 UTC); Postiz reproduces them within 15 minutes.

## Fix brief
# Security brief: Postiz: forged signed tokens and post-media path traversal let any registered user take over orgs and read server files (CVE-2026-115933, CVE-2026-115932)

Source: https://pwn.watch/i/postiz-account-takeover-file-read-cve-2026-115933 · status: live · severity: critical · updated Oct 24, 2026, 14:55 UTC

## Patch status
**PATCHED: fixed releases exist. Upgrade to a fixed version.**

## What it is
Two critical bugs in the self-hosted Postiz social media scheduler, both reported with working PoCs by Anthropic. Postiz signed session, invite and password-reset tokens with one shared secret and no purpose marker, and an extension-refresh route signed request data, so any registered user could forge tokens and become super admin of another organization (CVE-2026-115933, CVSS 9.9). A separate path traversal in post media let a registered user have the worker send any server file, including the JWT secret and env file, to their own Discord server (CVE-2026-115932, CVSS 9.6). Both are fixed in Postiz 2.25.3; self-registration is open by default, so upgrade now.

Severity detail: CVSS 9.9 (token forgery) and 9.6 (file read), any self-registered user, PoCs demonstrated end to end; no reported exploitation

- Product: Postiz (gitroomhq/postiz-app), self-hosted
- CVE / advisory ids: CVE-2026-115933, CVE-2026-115932

## Affected versions
- postiz-app 2.15.0 to before 2.25.3 (CVE-2026-115933, forged tokens)
- postiz-app 2.23.0 to before 2.25.3 (CVE-2026-115932, path traversal; main route needs the Discord provider configured)

## Check whether you're affected
No generic command applies (the product is a hosted service, appliance or desktop app). Check the installed version in its admin UI / About screen and compare with the versions above.

## Fix
Upgrade to one of these fixed versions (or later on the same branch):
- postiz-app 2.25.3

After upgrading, re-run the checks above and redeploy/restart the affected services.

## Secrets to rotate
This incident involves possible credential exposure. Rotate any credentials (API keys, tokens, env vars, SSH keys) that were present on affected systems or in affected builds while vulnerable/compromised versions were installed, and review access logs.

## Latest updates
- Oct 24, 2026: Postiz 2.25.3 ships fixes for PSA-2026-E9AHFV (CVE-2026-115932, path traversal) and PSA-2026-YT2HMH (CVE-2026-115933, forged tokens); all users are told to upgrade immediately. Workarounds until then: set DISABLE_REGISTRATION=true and block POST /integrations/extension-refresh at the reverse proxy.
- Oct 23, 2026: Anthropic reports both bugs to Postiz with working PoCs (17:45 UTC); Postiz reproduces them within 15 minutes.

## Advisories
- [PSA-2026-YT2HMH: Forged signed tokens let any registered user take over other users and organizations](https://gadvisory.org/advisories/PSA-2026-YT2HMH) (GAdvisory)
- [PSA-2026-E9AHFV: Path traversal in post media lets any registered user read server files](https://gadvisory.org/advisories/PSA-2026-E9AHFV) (GAdvisory)
- [CVE-2026-115933](https://www.cve.org/CVERecord?id=CVE-2026-115933) (CVE.org)
- [CVE-2026-115932](https://www.cve.org/CVERecord?id=CVE-2026-115932) (CVE.org)
- [Postiz v2.25.3 release](https://github.com/gitroomhq/postiz-app/releases/tag/v2.25.3) (GitroomHQ)

---
Machine-readable: https://pwn.watch/i/postiz-account-takeover-file-read-cve-2026-115933.json · all incidents: https://pwn.watch/incidents.json. Verify against the vendor advisory before changing production systems.