# CVE-2026-104651: Yaad Sarig Payment Gateway For WC < 2.2.13 - Subscriber+ Arbitrary Order Payment Manipulation via IDOR

> Authenticated users can manipulate other customers' orders due to missing authorization checks in the Yaad Sarig Payment Gateway plugin.

- **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:** 7 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-6pp4-6q7m-6492

## What is CVE-2026-104651?

CVE-2026-104651 is a medium-severity missing authorization vulnerability in Unknown Yaad Sarig Payment Gateway For WC, published on 7 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Yaad Sarig Payment Gateway For WC WordPress plugin before 2.2.13 does not verify authorization or that the requesting user owns the target order in several of its order payment-processing actions, allowing any authenticated user, including subscribers, to act on and alter orders belonging to other customers.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-104651 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-104651 is a medium-severity missing authorization vulnerability in Unknown Yaad Sarig Payment Gateway For WC, published on 7 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-104651 in the wild and no public exploit code.

Affected product: Unknown Yaad Sarig Payment Gateway For WC. 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-104651/ (Markdown: https://insights.sbomify.com/CVE-2026-104651/index.md)
```

## Sources

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

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