# CVE-2026-85037: Sunshine Photo Cart < 3.7 - Unauthenticated Price Manipulation via IDOR

> Unauthenticated attackers can manipulate cart prices to purchase items at lower costs, causing financial loss for site owners.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Sep 2026
- **Updated:** 9 Sep 2026
- **Also known as:** GHSA-6v37-8246-gmfc

## What is CVE-2026-85037?

CVE-2026-85037 is a medium-severity vulnerability in Unknown Sunshine Photo Cart, published on 9 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Sunshine Photo Cart  WordPress plugin before 3.7 does not validate that a client-supplied price identifier belongs to the item being purchased when it is added to the cart, allowing unauthenticated users to buy items at a lower price defined elsewhere on the site and complete an order at that price, resulting in financial loss for the site owner.

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

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


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

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

## Is CVE-2026-85037 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-85037 is a medium-severity vulnerability in Unknown Sunshine Photo Cart, published on 9 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-85037 in the wild and no public exploit code.

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

## Sources

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

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