# CVE-2026-93528: NP Quote Request for WooCommerce < 2.4.16 - Unauthenticated Order Data Disclosure via Quote Request Page

> Unauthenticated attackers can view other customers' order details by accessing the quote request page without ownership verification.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/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:** 23 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-7j8g-qcr9-g32j

## What is CVE-2026-93528?

CVE-2026-93528 is a low-severity vulnerability in Unknown NP Quote Request for WooCommerce, published on 23 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The NP Quote Request for WooCommerce WordPress plugin before 2.4.16 does not verify order ownership before rendering an order's details, allowing unauthenticated attackers to view another customer's order using the order's key.

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

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


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

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

## Is CVE-2026-93528 being exploited?

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

Public exploit code:

- Technical details, proof of concept, and responsible disclosure timeline for CVE-2026-93528 (Unauthenticated Order Data Disclosure in NP Quote Request for WooCommerce). (github_poc): https://github.com/muradislamzada/CVE-2026-93528

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93528 is a low-severity vulnerability in Unknown NP Quote Request for WooCommerce, published on 23 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-93528 in the wild and no public exploit code.

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

## Sources

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

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