# CVE-2026-108073: SureCart < 4.9.5 - Unauthenticated Private Catalog Data Disclosure via 'expand' Parameter


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

## What is CVE-2026-108073?

CVE-2026-108073 is a medium-severity vulnerability in Unknown SureCart, published on 21 Oct 2026. 

### Official description

The SureCart  WordPress plugin before 4.9.5 does not restrict which related objects an anonymous visitor may include when reading a single upsell funnel through its REST API, nor strip private fields from those objects, allowing unauthenticated users to read merchant-private catalog data such as pricing, commission, stock, SKU and tax internals, including unpublished products.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-108073 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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