# Postiz 2.25.3 closes critical file-read and token-forgery flaws

Cite as: Gloqo AI, "Postiz 2.25.3 closes critical file-read and token-forgery flaws", reviewed 24 Oct 2026, https://www.gloqo.ai/security-updates/advisories/postiz-2026-10-24/.

Gloqo reviewed the vendor and CNA records on 24 Oct 2026. Those sources are the authority for the vulnerability.

Product: Postiz
Published: 2026-10-24
Reviewed: 2026-10-24T22:11:28Z

## Summary

Registered users can exploit unrestricted provider methods to read backend files and crash the service (CVE-2026-115931), traverse post-media paths to read worker files (CVE-2026-115932), or obtain signed tokens for account and organization takeover (CVE-2026-115933). Exposed files can include JWT signing secrets and provider credentials.

## Affected

CVE-2026-115931 affects 2.23.0 through versions before 2.25.2; CVE-2026-115932 affects 2.23.0 through versions before 2.25.3; CVE-2026-115933 affects 2.15.0 through versions before 2.25.3. An ordinary account is required; self-registration is open by default.

## Fix

Upgrade to 2.25.3 to cover all three flaws; 2.25.2 fixes CVE-2026-115931 but not the other two. Setting DISABLE_REGISTRATION=true only reduces exposure to existing account holders. Leaving Discord credentials unset removes the main media-exfiltration route, not the alternate routes. If browser-extension channels are unused, blocking POST /integrations/extension-refresh removes the main token-signing route, not the invitation route. These workarounds do not replace the upgrade.

## Evidence

The CNA records describe researcher proof-of-concept demonstrations on unmodified builds, including file extraction, backend termination and cross-organization takeover. They do not state malicious exploitation in the wild.

## Severity

Postiz assigns CVSS v3.1 Critical scores of 9.9 to CVE-2026-115931 and CVE-2026-115933, and 9.6 to CVE-2026-115932.

## Context

The main media-exfiltration route requires a configured Discord provider; its credentials are empty in the shipped compose configuration. A validation route instead needs Dribbble, TikTok or Pinterest. The main token-forgery route requires outbound access to api2.skool.com. With Stripe billing configured, the attacker's plan must allow a channel and the target organization must not be on the STANDARD tier; session and password-reset token abuse is not subject to these limits. CVE-2026-115931 was published October 23 at 22:02 UTC; the other two records and the 2.25.3 release followed October 24.

## CVEs

- [CVE-2026-115931](https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/115xxx/CVE-2026-115931.json)
- [CVE-2026-115932](https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/115xxx/CVE-2026-115932.json)
- [CVE-2026-115933](https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/115xxx/CVE-2026-115933.json)

## Sources

1. [Postiz v2.25.3 security release, October 24](https://github.com/gitroomhq/postiz-app/releases/tag/v2.25.3)
2. [Postiz CNA record: CVE-2026-115931](https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/115xxx/CVE-2026-115931.json)
3. [Postiz CNA record: CVE-2026-115932](https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/115xxx/CVE-2026-115932.json)
4. [Postiz CNA record: CVE-2026-115933](https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/115xxx/CVE-2026-115933.json)
