Forged signed tokens let any registered user take over other users and organizations
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.
CVE-2026-115933
Primary source · Revision 1
Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.
Security context
Source reference: cve:CVE-2026-115933
postiz-app
Source reference: /containers/cna/affected/0/product
- Affected versions
- Not stated in this record
- Fixed versions
- Not stated in this record
- Prerequisites
- Not stated in this record
Structured affected-version data
Original package identities and version rules from this source.
[
{
"repo": "https://github.com/gitroomhq/postiz-app",
"vendor": "GitroomHQ",
"product": "postiz-app",
"versions": [
{
"status": "affected",
"version": "2.15.0",
"lessThan": "2.25.3",
"versionType": "semver"
}
],
"packageName": "postiz-app",
"defaultStatus": "unaffected"
}
]- Related CVEs
- CVE-2026-115933
Source reference:
/cveMetadata/cveId
Publisher severity
critical
Source reference: /containers/cna/metrics
- Event
- #55825 · Revision 1
- Added to Heist Feed
- Publisher date