# CVE-2026-100145: Synchrony Financing 1.0.5 - 1.1.1 - Unauthenticated Order Takeover via admin_order_callback REST Route


- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-mr5q-g9rw-x79g

## What is CVE-2026-100145?

CVE-2026-100145 is a medium-severity vulnerability in Unknown Synchrony Financing, published on 21 Oct 2026. 

### Official description

The Synchrony Financing WordPress plugin before 1.1.2 does not properly authorise requests to one of its REST routes that modifies WooCommerce orders, allowing unauthenticated attackers to reassign any order to an account they control, tamper with its details, and read the associated customer's personal data.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-100145 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100145 is a medium-severity vulnerability in Unknown Synchrony Financing, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-100145 in the wild and no public exploit code.

Affected product: Unknown Synchrony Financing. 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-100145/ (Markdown: https://insights.sbomify.com/CVE-2026-100145/index.md)
```

## Sources

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

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