# CVE-2026-107429: WordPress Paid Videochat Turnkey Site plugin <= 7.5.12 - Other vulnerability Type vulnerability

> Attackers can manipulate input data in the Paid Videochat Turnkey Site plugin due to improper quantity validation, potentially altering application state.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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:** 12 Oct 2026
- **Updated:** 12 Oct 2026
- **Also known as:** GHSA-vwjq-q23m-774h

## What is CVE-2026-107429?

CVE-2026-107429 is a medium-severity vulnerability in VideoWhisper.com Paid Videochat Turnkey Site, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper Validation of Specified Quantity in Input vulnerability in VideoWhisper.com Paid Videochat Turnkey Site ppv-live-webcams allows Input Data Manipulation.This issue affects Paid Videochat Turnkey Site: from n/a through 7.5.12.

Weakness: CWE-1284 (Improper Validation of Specified Quantity in Input)

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


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

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

## Is CVE-2026-107429 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-107429 is a medium-severity vulnerability in VideoWhisper.com Paid Videochat Turnkey Site, published on 12 Oct 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-107429 in the wild and no public exploit code.

Affected product: VideoWhisper.com Paid Videochat Turnkey Site. 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-107429/ (Markdown: https://insights.sbomify.com/CVE-2026-107429/index.md)
```

## Sources

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

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