# CVE-2026-16612: FiboSearch < 1.34.1 - Unauthenticated Password-Protected Product Information Disclosure

> Unauthenticated attackers can access password-protected product details and metadata via AJAX endpoints in the FiboSearch WordPress 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:** 22 Aug 2026
- **Updated:** 23 Aug 2026
- **Also known as:** GHSA-qmf2-8gx3-xf2c

## What is CVE-2026-16612?

CVE-2026-16612 is a medium-severity vulnerability in Unknown FiboSearch, published on 22 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The FiboSearch  WordPress plugin before 1.34.1 does not consistently exclude password-protected products from its unauthenticated AJAX endpoints, allowing unauthenticated users to disclose and enumerate password-protected products and their metadata without entering the product password. Two endpoints are affected: the autocomplete search endpoint (dgwt_wcas_ajax_search) and the Details Panel endpoint (dgwt_wcas_result_details) when queried for taxonomy details.

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

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


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

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

## Is CVE-2026-16612 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16612 is a medium-severity vulnerability in Unknown FiboSearch, published on 22 Aug 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-16612 in the wild and no public exploit code.

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

## Sources

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

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