# CVE-2025-0614: Input validation vulnerability in Qualifio's Wheel of Fortune

> Attackers can bypass email validation to win prizes multiple times by manipulating case sensitivity in the Qualifio Wheel of Fortune application.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:** 21 Jan 2025
- **Updated:** 21 Jan 2025
- **Also known as:** GHSA-2jx6-v8vf-jjp6

## What is CVE-2025-0614?

CVE-2025-0614 is a medium-severity vulnerability in Qualifio Wheel of fortune, published on 21 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Input validation vulnerability in Qualifio's Wheel of Fortune. This vulnerability could allow an attacker to modify a single email to contain upper and lower case characters in order to access the application and win prizes as many times as wanted.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2025-0614 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-0614 is a medium-severity vulnerability in Qualifio Wheel of fortune, published on 21 Jan 2025. 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-2025-0614 in the wild and no public exploit code.

Affected product: Qualifio Wheel of fortune. 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-0614/ (Markdown: https://insights.sbomify.com/CVE-2025-0614/index.md)
```

## Sources

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

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