# CVE-2026-19127: Insufficient verification of lifetime-deal redemption codes allows forgery of permanent paid subscriptions

> Attackers can forge redemption codes to obtain permanent paid subscriptions without payment, bypassing billing authorization in Postiz.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2026
- **Updated:** 7 Aug 2026

## What is CVE-2026-19127?

CVE-2026-19127 is a medium-severity vulnerability in GitroomHQ postiz-app, published on 6 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2026-19127?


## How do I fix CVE-2026-19127?

No fix has been published for CVE-2026-19127 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-19127 being exploited?

There is no known exploitation of CVE-2026-19127 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-19127 and fix it if it is affected.

What it is: CVE-2026-19127 is a medium-severity vulnerability in GitroomHQ postiz-app, published on 6 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-19127 in the wild and no public exploit code.

Affected product: GitroomHQ postiz-app. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-19127/ (Markdown: https://insights.sbomify.com/CVE-2026-19127/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-19127
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-19127
- OSV: https://osv.dev/vulnerability/CVE-2026-19127

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-19127/
Summaries are generated and may contain mistakes; the official description above is the record.