CVE-2026-16612: FiboSearch: unauthenticated AJAX leaks password-protected products
AWAITING NVDFiboSearch, a WooCommerce/WordPress product search plugin, fails to exclude password-protected products from its unauthenticated autocomplete and details-panel AJAX endpoints (dgwt_wcas_ajax_search and dgwt_wcas_result_details), letting anonymous visitors enumerate and view metadata for products that should require a password to view. This is not an AI/ML vulnerability — the ai_category tag appears to be a misclassification, as FiboSearch is a conventional PHP/WordPress search plugin with no model, inference, or agent component involved. There is no CVSS score, no EPSS data, no public exploit, no Nuclei template, and it is not in CISA KEV, so exploitation is low-effort (simple HTTP requests) but currently unweaponized and unranked. Because it sits outside the AI/ML attack surface this platform tracks, it carries no bearing on AI supply chain, model, or inference risk and should not be prioritized in an AI threat intelligence workflow; site operators running FiboSearch on WordPress/WooCommerce should still upgrade to 1.34.1+ as routine WordPress patch hygiene. No detection or compensating control specific to AI systems is applicable here.
What is the risk?
Low relevance to AI/ML risk. The flaw is a straightforward authorization/access-control gap in a WordPress e-commerce search plugin: unauthenticated users can query two AJAX endpoints and receive data (product existence, metadata, taxonomy details) that should be gated behind a product password. Exploitability is trivial (no auth, no special tooling, just crafted HTTP requests to public endpoints) but impact is limited to confidentiality of intentionally-restricted product listings — not code execution, not data destruction, not system compromise. No CVSS/EPSS scoring is available, no KEV listing, and no public PoC or scanner template exists yet, so real-world exploitation activity is unconfirmed.
How does the attack unfold?
What systems are affected?
| Package | Ecosystem | Vulnerable Range | Patched |
|---|---|---|---|
| FiboSearch | — | — | No patch |
Do you use FiboSearch? You're affected.
How severe is it?
What should I do?
1 step-
For WordPress/WooCommerce site operators running FiboSearch: upgrade to version 1.34.1 or later, which is reported to consistently exclude password-protected products from both the dgwt_wcas_ajax_search autocomplete endpoint and the dgwt_wcas_result_details taxonomy-details endpoint. As a temporary workaround, restrict or monitor access to these AJAX actions at the WAF/reverse-proxy layer, and review WooCommerce password-protected product usage to confirm no sensitive unreleased or restricted-access product data was exposed. No AI-specific detection or mitigation applies since this is not an AI/ML system.
How is it classified?
Which compliance frameworks are affected?
Compliance analysis pending. Sign in for full compliance mapping when available.
Frequently Asked Questions
What is CVE-2026-16612?
FiboSearch, a WooCommerce/WordPress product search plugin, fails to exclude password-protected products from its unauthenticated autocomplete and details-panel AJAX endpoints (dgwt_wcas_ajax_search and dgwt_wcas_result_details), letting anonymous visitors enumerate and view metadata for products that should require a password to view. This is not an AI/ML vulnerability — the ai_category tag appears to be a misclassification, as FiboSearch is a conventional PHP/WordPress search plugin with no model, inference, or agent component involved. There is no CVSS score, no EPSS data, no public exploit, no Nuclei template, and it is not in CISA KEV, so exploitation is low-effort (simple HTTP requests) but currently unweaponized and unranked. Because it sits outside the AI/ML attack surface this platform tracks, it carries no bearing on AI supply chain, model, or inference risk and should not be prioritized in an AI threat intelligence workflow; site operators running FiboSearch on WordPress/WooCommerce should still upgrade to 1.34.1+ as routine WordPress patch hygiene. No detection or compensating control specific to AI systems is applicable here.
Is CVE-2026-16612 actively exploited?
No confirmed active exploitation of CVE-2026-16612 has been reported, but organizations should still patch proactively.
How to fix CVE-2026-16612?
For WordPress/WooCommerce site operators running FiboSearch: upgrade to version 1.34.1 or later, which is reported to consistently exclude password-protected products from both the dgwt_wcas_ajax_search autocomplete endpoint and the dgwt_wcas_result_details taxonomy-details endpoint. As a temporary workaround, restrict or monitor access to these AJAX actions at the WAF/reverse-proxy layer, and review WooCommerce password-protected product usage to confirm no sensitive unreleased or restricted-access product data was exposed. No AI-specific detection or mitigation applies since this is not an AI/ML system.
What is the CVSS score for CVE-2026-16612?
No CVSS score has been assigned yet.
What are the technical details?
Original Advisory
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.
Exploitation Scenario
An unauthenticated visitor to a WooCommerce store using FiboSearch sends autocomplete queries to the dgwt_wcas_ajax_search endpoint, or requests taxonomy details via dgwt_wcas_result_details, matching terms associated with password-protected products (e.g. unreleased items, VIP/restricted catalog entries). The plugin returns product names, metadata, and taxonomy details without checking the password-protection flag, letting the visitor enumerate and inspect restricted products they should not be able to discover, bypassing the intended access gate entirely without needing credentials.
References
- wpscan.com/vulnerability/705cf14a-2782-408a-80b1-be7a9da6bbdd/ exploit vdb-entry technical-description
Timeline
Related Vulnerabilities
CVE-2025-5120 10.0 smolagents: sandbox escape enables unauthenticated RCE
Same attack type: Data Leakage CVE-2023-3765 10.0 MLflow: path traversal allows arbitrary file read
Same attack type: Data Leakage CVE-2025-2828 10.0 LangChain RequestsToolkit: SSRF exposes cloud metadata
Same attack type: Auth Bypass CVE-2025-53767 10.0 Azure OpenAI: SSRF EoP, no auth required (CVSS 10)
Same attack type: Privacy Violation CVE-2026-21858 10.0 n8n: Input Validation flaw enables exploitation
Same attack type: Auth Bypass