# CVE-2026-88929: Sale Booster 7.0.0 - 7.5.1 - Unauthenticated Non-Public Product Disclosure

> Unauthenticated attackers can read details of draft, pending, and private products in the Sale Booster WooCommerce plugin.

- **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
- **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-fvx4-2974-ggpj

## What is CVE-2026-88929?

CVE-2026-88929 is a medium-severity vulnerability in Unknown Product Badge, Label, Countdown Timer 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 Product Badge, Label, Countdown Timer for WooCommerce  WordPress plugin before 7.5.2 does not check whether a product is published before returning its details to unauthenticated users, allowing them to read the title, description and price of draft, pending and private products.

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

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


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

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

## Is CVE-2026-88929 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-88929 is a medium-severity vulnerability in Unknown Product Badge, Label, Countdown Timer 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-88929 in the wild and no public exploit code.

Affected product: Unknown Product Badge, Label, Countdown Timer 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-88929/ (Markdown: https://insights.sbomify.com/CVE-2026-88929/index.md)
```

## Sources

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

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