# CVE-2026-132222: BizPrint before 4.10.0 Missing Authorization via Debug AJAX Handlers


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 18 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-jqgp-4hw7-fg35

## What is CVE-2026-132222?

CVE-2026-132222 is a medium-severity vulnerability in bizswoop BizPrint – Automatic Order Printing for WooCommerce, published on 18 Nov 2026. 

### Official description

BizPrint (print-google-cloud-print-gcp-woocommerce) before 4.10.0 contains a missing authorization vulnerability in its Debug\Core component that allows any authenticated user, including the lowest-privilege Subscriber role, to invoke the getPrinters and sendPrintRequest AJAX actions without a nonce or capability check. Attackers can send a crafted admin-ajax.php request with an arbitrary WooCommerce order_id to dispatch print jobs for other customers' orders and disclose printer configuration, exposing cross-customer PII and abusing printer resources.

Weakness: CWE-862 (Missing Authorization)

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


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

Upgrade bizswoop BizPrint – Automatic Order Printing for WooCommerce to 4.10.0 or later. The advisory says that version fixes it.

## Is CVE-2026-132222 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-132222 is a medium-severity vulnerability in bizswoop BizPrint – Automatic Order Printing for WooCommerce, published on 18 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-132222 in the wild and no public exploit code.

Affected product: bizswoop BizPrint – Automatic Order Printing for WooCommerce. 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-132222/ (Markdown: https://insights.sbomify.com/CVE-2026-132222/index.md)
```

## Sources

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

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