A second, narrower route that creates team invitations signs extra fields from the request body in the same way.
Metrics
Affected Vendors & Products
No advisories yet.
Solution
No solution given by the vendor.
Workaround
If you do not use channels that rely on the Postiz browser extension, block POST /integrations/extension-refresh at your reverse proxy. This removes the main signing route; the team invitation route remains.
Sat, 24 Oct 2026 16:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Gitroomhq
Gitroomhq postiz-app |
|
| Vendors & Products |
Gitroomhq
Gitroomhq postiz-app |
Sat, 24 Oct 2026 14:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Postiz signs its session, invitation and password reset tokens with one shared secret and without any marker of what a token is for. A route that refreshes the credentials of a browser-extension channel signed data taken from the request itself and stored the result where the requesting user can read it back. A user could therefore obtain a validly signed token containing any claims they choose, which the application accepts as a session, as an organization invitation with a chosen role, as a password reset or as an enterprise provisioning token. A second, narrower route that creates team invitations signs extra fields from the request body in the same way. | |
| Title | Forged signed tokens let any registered user take over other users and organizations | |
| Weaknesses | CWE-290 CWE-345 CWE-915 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: postiz
Published:
Updated: 2026-10-24T14:29:17.141Z
Reserved: 2026-10-23T21:21:06.893Z
Link: CVE-2026-115933
No data.
Status : Received
Published: 2026-10-24T15:17:33.957
Modified: 2026-10-24T15:17:33.957
Link: CVE-2026-115933
No data.
OpenCVE Enrichment
Updated: 2026-10-24T16:15:17Z