# CVE-2026-19436: Ultimate Gift Cards For WooCommerce < 3.2.10 - Unauthenticated Gift Card Value Inflation via Discounted Purchase

> Unauthenticated attackers can inflate gift card values by exploiting a lack of price reconciliation, gaining store credit worth more than paid.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Sep 2026
- **Updated:** 10 Sep 2026
- **Also known as:** GHSA-5j4r-9728-477v

## What is CVE-2026-19436?

CVE-2026-19436 is a high-severity vulnerability in Unknown Ultimate Gift Cards for WooCommerce, published on 10 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Ultimate Gift Cards for WooCommerce WordPress plugin before 3.2.10 does not reconcile the value of the gift card coupon it issues against the amount actually collected at checkout, allowing unauthenticated users to obtain store credit worth more than they paid.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-19436 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19436 is a high-severity vulnerability in Unknown Ultimate Gift Cards for WooCommerce, published on 10 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-19436 in the wild and no public exploit code.

Affected product: Unknown Ultimate Gift Cards for WooCommerce. 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-19436/ (Markdown: https://insights.sbomify.com/CVE-2026-19436/index.md)
```

## Sources

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

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