Forged signed tokens let any registered user take over other users and organizations
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| GitroomHQ | postiz-app | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Gitroomhq | Postiz-app |
|
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.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.249% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Gitroomhq
Gitroomhq postiz-app |
|
| Vendors & Products |
Gitroomhq
Gitroomhq postiz-app |
| 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
|