CVE-2026-107761 PUBLISHED

Channel tokens and organization API key exposed in API responses

Assigner: postiz
Reserved: 08.10.2026 Published: 11.10.2026 Updated: 11.10.2026

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.

Metrics

CVSS Vector: 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
CVSS Score: 5.3

Product Status

Vendor GitroomHQ
Product postiz-app
Versions Default: unaffected
  • affected from 0 to 2.25.1 (excl.)

Credits

  • Gilad Resisi reporter
  • Enno Gelhaus coordinator
  • Gilad Resisi remediation developer

References

Problem Types

  • CWE-201 CWE
  • CWE-213 CWE

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.