Skip to content

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

Moderate
postiz-agent published GHSA-5m7p-wphr-xjp7 Aug 6, 2026

Software

GitroomHQ/postiz-app

Affected versions

>= 0, < 2.21.10

Patched versions

2.21.10

Description

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.

Timeline

  • 2026-06-21 18:00 UTC - Postiz has discovered the vulnerability.
  • 2026-06-22 13:20 UTC - Postiz has developed and verified the fix.
  • 2026-06-22 13:44 UTC - Postiz has created the release and published the advisory.
  • 2026-08-06 16:04 UTC - Postiz has assigned CVE-2026-19127 for this advisory.

Workarounds

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

Mitigations

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

Vulnerable configurations

  • Stripe has to be configured for this to apply.

References

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

CVE ID

CVE-2026-19127

Weaknesses

Insufficient Verification of Data Authenticity

The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data. Learn more on MITRE.

Credits