Paid subscription activation via unverified lifetime codes
Published Aug 6, 2026 · Updated Aug 6, 2026
Business-logic flaw in Postiz before 2.21.10 allows remote authenticated users to activate permanent paid subscriptions using forged codes. The POST /billing/lifetime route passes an organization identifier and attacker-supplied code to lifetimeDeal without adequately verifying code authenticity or single-use state. A valid Postiz account and configured Stripe integration are required; successful exploitation grants the highest lifetime tier without payment.
Summary
What happened
Business-logic flaw in Postiz before 2.21.10 allows remote authenticated users to activate permanent paid subscriptions using forged codes. The POST /billing/lifetime route passes an organization identifier and attacker-supplied code to lifetimeDeal without adequately verifying code authenticity or single-use state. A valid Postiz account and configured Stripe integration are required; successful exploitation grants the highest lifetime tier without payment.
The record
- CVE
- CVE-2026-19127
- Published
- Aug 6, 2026
- Updated
- Aug 6, 2026
- Vendor
- GitroomHQ
- Product
- Postiz
- Classifications
- CWE-345
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 6, 2026CVE publishedPublication date reported by the CVE source.
- Aug 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.21.10
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo