PSA-2026-4QX1WGCVE-2026-107761GCVE-125-2026-4QX1WGOctober 11, 2026Channel tokens and organization API key exposed in API responses
Two authenticated Postiz endpoints returned the full database row instead of the fields the client needs. Deleting a channel through the public API returned that channel's platform access and refresh tokens to the calling OAuth app, and GET /user/organizations returned the organization API key to every member, although it is meant to be visible to admins only.
Affected (1)
- GitroomHQpostiz-app
- ≥ 0Fixed in 2.25.1
Overview
Several Postiz endpoints return the complete database row of the record they operate on instead of only the fields the client needs. Two of them include secrets the caller is not meant to receive.
The public API's channel delete returns the deleted integration row, including the channel's platform access token and refresh token. A third-party OAuth app permitted to delete a channel therefore receives that channel's social platform credentials and can use them against the connected account directly, outside Postiz.
GET /user/organizations returns each organization row, including its API key, to every member of the organization. The API key is intended for admins only, so a member with a lower role can obtain it and call the public API on behalf of the organization.
Both endpoints require a valid session, API key or OAuth token and are scoped to the caller's own organization. There is no anonymous access and no cross-tenant exposure.
Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:L/SA:N- Attack vector
- Network
- Attack complexity
- Low
- Attack requirements
- None
- Privileges required
- Low
- User interaction
- None
- Confidentiality (vulnerable system)
- Low
- Integrity (vulnerable system)
- None
- Availability (vulnerable system)
- None
- Confidentiality (subsequent system)
- Low
- Integrity (subsequent system)
- Low
- Availability (subsequent system)
- None
Weaknesses (2)
References (2)
Credits (3)
- Gilad ResisiReporter · @giladresisi
- Enno GelhausCoordinator · @egelhaus
- Gilad ResisiRemediation developer · @giladresisi
Context
Impacts
A third-party OAuth app permitted to delete a channel obtains that channel's social platform access and refresh tokens and can act on the connected account outside Postiz.
An organization member without the admin role obtains the organization API key and can use the public API on behalf of the organization.
Timeline
- 10/01/2026 08:13
Postiz has discovered the vulnerability.
- 10/08/2026 05:03
Postiz has developed and verified a patch.
- 10/11/2026 15:16
Postiz has created the release and published the advisory.