# CVE-2025-10778: Smartstore Gift Voucher confirm race condition

> Attackers can exploit a race condition in the Gift Voucher confirmation process to potentially manipulate voucher states, requiring high complexity and permissions.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X`)
- **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:** 22 Sep 2025
- **Updated:** 22 Sep 2025
- **Also known as:** GHSA-326h-w5x2-4vrm

## What is CVE-2025-10778?

CVE-2025-10778 is a low-severity vulnerability in Smartstore, published on 22 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability has been found in Smartstore up to 6.2.0. The affected element is an unknown function of the file /checkout/confirm/ of the component Gift Voucher Handler. The manipulation leads to race condition. The attack may be initiated remotely. The attack's complexity is rated as high. The exploitability is described as difficult. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2025-10778?


## How do I fix CVE-2025-10778?

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

## Is CVE-2025-10778 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-10778 and fix it if it is affected.

What it is: CVE-2025-10778 is a low-severity vulnerability in Smartstore, published on 22 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-10778 in the wild and no public exploit code.

Affected product: Smartstore. 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-2025-10778/ (Markdown: https://insights.sbomify.com/CVE-2025-10778/index.md)
```

## Sources

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

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