# CVE-2026-133114: Caddy WooCommerce Side Cart 3.0.0 before 3.2.1 Missing Authorization via saved-items REST endpoint


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

## What is CVE-2026-133114?

CVE-2026-133114 is a medium-severity vulnerability in Caddy – WooCommerce Side Cart & Free Shipping Bar, published on 19 Nov 2026. 

### Official description

Caddy – WooCommerce Side Cart & Free Shipping Bar plugin for WordPress 3.0.0 before 3.2.1 contains a missing authorization vulnerability in the saved-items/add REST endpoint that exposes non-public product data. Authenticated attackers with Subscriber-level access can enumerate product_id values to read names, prices, images and stock status of private, draft, hidden and password-protected products.

Weakness: CWE-862 (Missing Authorization)

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


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

Upgrade Caddy – WooCommerce Side Cart & Free Shipping Bar to 3.2.1 or later. The advisory says that version fixes it.

## Is CVE-2026-133114 being exploited?

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

Public exploit code:

- CVE-2026-133114 -- Caddy WooCommerce Side Cart <3.2.1 Missing Authorization (Unauthenticated PII Access). CVSS 8.2 High. (github_poc): https://github.com/LLCForge/CVE-2026-133114

## Fix prompt for AI coding agents

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

What it is: CVE-2026-133114 is a medium-severity vulnerability in Caddy – WooCommerce Side Cart & Free Shipping Bar, published on 19 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-133114 in the wild and no public exploit code.

Affected product: Caddy – WooCommerce Side Cart & Free Shipping Bar. 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-133114/ (Markdown: https://insights.sbomify.com/CVE-2026-133114/index.md)
```

## Sources

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

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