# CVE-2026-96669: Food Store <= 1.5.5 - Unauthenticated Stored Cross-Site Scripting via 'service_type' Cookie


- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-cx7q-6956-p3vx

## What is CVE-2026-96669?

CVE-2026-96669 is a high-severity vulnerability in wpscripts Food Store – Online Food Delivery & Pickup, published on 29 Oct 2026. 

### Official description

The Food Store – Online Food Delivery & Pickup plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'service_type' Cookie in all versions up to, and including, 1.5.5 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The attack is seeded unauthenticated by supplying a payload via the ?type= query parameter on the public checkout page, which the plugin writes directly into the browser's service_type cookie; this cookie value is later persisted to order meta and rendered unescaped in the admin panel.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-96669 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-96669 is a high-severity vulnerability in wpscripts Food Store – Online Food Delivery & Pickup, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-96669 in the wild and no public exploit code.

Affected product: wpscripts Food Store – Online Food Delivery & Pickup. 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-96669/ (Markdown: https://insights.sbomify.com/CVE-2026-96669/index.md)
```

## Sources

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

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