CVE-2026-19127

Insufficient verification of lifetime-deal redemption codes allows forgery of permanent paid subscriptions

Published Aug 6, 2026 CVSS 3.1 · 6.5 Medium EPSS < 1% KEV · Not listed
Description
An issue in the billing and license activation subsystem allows remote attackers to bypass payment authorization workflows. By exploiting insufficient cryptographic validation or lack of server-side state verification on promotional/lifetime-deal (LTD) redemption codes, an unauthenticated attacker can forge valid redemption tokens or replay existing single-use codes to activate permanent, tier-highest paid subscriptions without a financial transaction.

Analysis

AI-generated

Technical impact

An issue in the billing and license activation subsystem of Postiz App allows remote attackers to bypass payment authorization by forging or replaying promotional or lifetime‑deal redemption codes. The flaw arises from insufficient cryptographic verification and the absence of server‑side state checks (CWE‑345), enabling attackers to create valid tokens or reuse single‑use ones to activate permanent, top‑tier paid subscriptions without any payment. The likely attack vector is remote exploitation through the subscription activation API using forged or replayed redemption codes.

Affected Systems

The affected product is Postiz App developed by GitroomHQ. The vulnerability was addressed in release v2.21.10; older versions lack the fix, but no specific version range was enumerated in the advisory.

Risk and Exploitability

The CVSS score of 6.5 indicates moderate severity. The EPSS score is unavailable, and the vulnerability is not listed in the CISA KEV catalog, implying no known active exploitation. However, the flaw permits unauthenticated remote attackers to grant themselves or others paid access, potentially causing significant financial loss. The attack requires only the ability to request the billing API; there is no prerequisite of authentication, making the exploit relatively low effort.

Remediation

Vendor Solution

No solution other than upgrading to v2.21.10 is currently known.


Vendor Workaround

No workaround other than upgrading to v2.21.10 is currently known.


OpenCVE Recommended Actions

  • Upgrade to Postiz App version 2.21.10 or later, which includes the patch for redemption code validation bugs.
  • Implement additional server‑side checks to confirm the redemption token is cryptographically signed, has not been previously used, and corresponds to a valid active promotional offer.
  • Monitor subscription activation logs for abnormal patterns and apply rate limiting to the activation endpoint to mitigate automated forgery attempts.

Generated by OpenCVE AI on August 7, 2026 at 01:25 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Gitroomhq
Gitroomhq postiz-app
Vendors & Products Gitroomhq
Gitroomhq postiz-app
Type Values Removed Values Added
Description An issue in the billing and license activation subsystem allows remote attackers to bypass payment authorization workflows. By exploiting insufficient cryptographic validation or lack of server-side state verification on promotional/lifetime-deal (LTD) redemption codes, an unauthenticated attacker can forge valid redemption tokens or replay existing single-use codes to activate permanent, tier-highest paid subscriptions without a financial transaction.
Title Insufficient verification of lifetime-deal redemption codes allows forgery of permanent paid subscriptions
Weaknesses CWE-345
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N'}

Weaknesses
  • CWE-345

    Insufficient Verification of Data Authenticity

Sources

Status
PUBLISHED
Assigner
postiz
Published
Updated
Aug 7, 2026, 2:03 PM
Reserved
Aug 6, 2026, 3:49 PM
Status
Deferred
Published
Aug 6, 2026, 10:16 PM
Modified
Oct 23, 2026, 9:10 PM