Postiz App
Approved changes feed: RSS · Atom
cpe:2.3:a:gitroomhq:postiz-app:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Gitroomhq (b57ab359-f80c-54c2-b661-2e146779a95f) |
|---|---|
| Product | Postiz App (49b1db27-6ccb-552e-a286-911180c46b9c) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-107761 |
vulnerable | 2026-11-03 10:15:59.412371 |
Channel tokens and organization API key exposed in API responses
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.
Published: 2026-10-11T15:23:15.196Z
Updated: 2026-10-15T18:09:42.965Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-115931 |
vulnerable | 2026-11-03 10:15:37.627279 |
Arbitrary file read and backend crash through unrestricted provider method calls
CRITICAL (9.9)
Postiz lets a signed-in user ask the backend to run a function on one of their connected channels. The backend did not restrict which functions can be requested, so a user could call internal helper functions that were never meant to be reachable from the web interface.
One of those helpers reads a file from the server's disk. A user who connects a channel whose stored token is a file path can have the backend return the contents of any file it can read, including its environment, which holds the secret used to sign login sessions, the database address and the credentials of connected services. Another helper makes the backend process exit with a single request. Self-registration is open by default, so no existing account and no action by another user is needed.
Published: 2026-10-23T22:02:21.717Z
Updated: 2026-11-02T15:07:14.710Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-115933 |
vulnerable | 2026-11-03 10:15:37.510891 |
Forged signed tokens let any registered user take over other users and organizations
CRITICAL (9.9)
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.
Published: 2026-10-24T14:17:05.755Z
Updated: 2026-11-02T14:12:51.289Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-115932 |
vulnerable | 2026-11-03 10:15:37.264219 |
Path traversal in post media lets any registered user read server files
CRITICAL (9.6)
When a post is published, Postiz treats a media path that is not a web address as a file on the server's disk, but it does not check that the file lies inside the upload directory. A registered user can store a crafted media path with a post, get it past the checks that normally restrict it, and have the publishing worker read an arbitrary file and send it as an attachment to a Discord server the user controls.
The same unconfined reads can be reached through two further routes. One tells the caller whether a file exists and can exhaust the backend's memory, the other delivers the file the same way as the main route. Self-registration is open by default, so the attacker needs no existing account.
Published: 2026-10-24T12:28:36.033Z
Updated: 2026-11-02T14:07:12.305Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-94455 |
vulnerable | 2026-10-13 12:28:38.860081 |
Unauthenticated /enterprise/create-user mints lifetime top-tier organizations and discloses their API key
HIGH (7.1)
An HTTP endpoint intended for provisioning enterprise and reseller organisations is reachable without any session. The authentication middleware is bound only to an explicit list of controllers, and the enterprise controller is not on that list, so no authentication runs for these routes.
The endpoint's only check is that the request body carries a token bearing a valid signature from the instance secret. It does not check what that token was issued for. Login tokens are signed with the same secret and carry no purpose, audience or expiry claim, so an ordinary user's own session token satisfies the check.
Presented with such a token, the endpoint creates a new organisation holding the highest subscription tier, flagged as lifetime and with a channel allowance far above any sold plan, creates an organisation-owner account alongside it, and returns the new organisation's API key in the response body. That key is immediately valid against the public API.
Published: 2026-09-22T16:17:00.413Z
Updated: 2026-09-22T18:14:13.947Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-94456 |
vulnerable | 2026-10-13 12:28:38.715124 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-19127 |
vulnerable | 2026-09-16 04:34:15.690723 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-19264 |
vulnerable | 2026-09-16 04:34:15.258050 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-48799 |
vulnerable | 2026-07-29 00:55:01.659473 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-48783 |
vulnerable | 2026-07-29 00:55:01.641557 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-48781 |
vulnerable | 2026-07-29 00:55:01.636350 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-42556 |
vulnerable | 2026-06-08 08:03:16.496410 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-42346 |
vulnerable | 2026-06-08 08:03:16.184149 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-42298 |
vulnerable | 2026-06-08 08:03:16.138232 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-40487 |
vulnerable | 2026-06-08 08:01:20.788965 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-40168 |
vulnerable | 2026-06-08 08:01:19.982800 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-34590 |
vulnerable | 2026-06-08 07:59:12.728084 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-34577 |
vulnerable | 2026-06-08 07:59:12.711157 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-34576 |
vulnerable | 2026-06-08 07:59:12.709866 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-53641 |
vulnerable | 2026-06-08 07:31:14.842827 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.