# CVE-2026-15039: Gift Cards For WooCommerce Pro < 4.2.10 - Unauthenticated Arbitrary File Upload

> Unauthenticated attackers can upload arbitrary files, including PHP, leading to remote code execution in the Gift Cards For WooCommerce Pro plugin.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Aug 2026
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-h5c4-q3vg-m4m7

## What is CVE-2026-15039?

CVE-2026-15039 is a critical vulnerability in Unknown giftware, published on 12 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The giftware WordPress plugin before 4.2.10 does not validate the type of uploaded files in one of its upload paths, allowing unauthenticated users to upload arbitrary files, including PHP code, which can lead to remote code execution.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

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

## Is CVE-2026-15039 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15039 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15039 is a critical vulnerability in Unknown giftware, published on 12 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15039 exists.

Affected product: Unknown giftware. 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-15039/ (Markdown: https://insights.sbomify.com/CVE-2026-15039/index.md)
```

## Sources

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

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