# CVE-2026-0750: Payment bypass in Commerce Paybox

> Attackers can bypass payment verification in Drupal Commerce Paybox due to improper cryptographic signature checks, allowing unauthorized transactions.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Jan 2026
- **Updated:** 28 Jan 2026
- **Also known as:** CLSA-2026-1789633542, GHSA-mxrg-rhmf-2mjf

## What is CVE-2026-0750?

CVE-2026-0750 is a high-severity authentication bypass vulnerability in Drupal Commerce Paybox, published on 28 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper Verification of Cryptographic Signature vulnerability in Drupal Drupal Commerce Paybox Commerce Paybox on Drupal 7.X allows Authentication Bypass.This issue affects Drupal Commerce Paybox: from 7-x-1.0 through 7.X-1.5.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

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

It affects 1 product.


Products: Verifone Commerce Paybox.

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

Apply the vendor's patch.

## Is CVE-2026-0750 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-0750 is a high-severity authentication bypass vulnerability in Drupal Commerce Paybox, published on 28 Jan 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-0750 in the wild and no public exploit code.

Affected product: Drupal Commerce Paybox. 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-0750/ (Markdown: https://insights.sbomify.com/CVE-2026-0750/index.md)
```

## Sources

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

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