CVE-2026-115933
Received Received - Intake

Session Token Forgery in Postiz

Vulnerability report for CVE-2026-115933, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-24

Last updated on: 2026-10-24

Assigner: postiz

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-24
Last Modified
2026-10-24
Generated
2026-10-24
AI Q&A
2026-10-24
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
GitroomHQ postiz-app 2.15.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-915 The product receives input from an upstream component that specifies multiple attributes, properties, or fields that are to be initialized or updated in an object, but it does not properly control which attributes can be modified.
CWE-345 The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.
CWE-290 This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in Postiz allows any registered user to forge signed tokens by exploiting the Skool account integration. The shared secret used for signing session, invitation, and password reset tokens enables attackers to create valid tokens with arbitrary claims. This includes impersonating users, resetting passwords, or joining organizations as super administrators.

Impact Analysis

An attacker could gain unauthorized access to accounts, reset passwords for other users, join organizations with elevated privileges, or access sensitive data like API keys. This could lead to data breaches, privilege escalation, and full system compromise.

Compliance Impact

This vulnerability likely violates compliance requirements for data protection and access control. GDPR requires strict access controls and breach notification, while HIPAA mandates safeguards for sensitive health data. Unauthorized access could lead to regulatory penalties and legal consequences.

Mitigation Strategies
  • Upgrade Postiz to version 2.25.3 or later to apply the official fix addressing the token forgery vulnerability.
  • Block the extension-refresh endpoint at the reverse proxy level to prevent unauthorized token generation.
  • Disable self-registration or set DISABLE_REGISTRATION=true to reduce attack surface.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-115933. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart