Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CVE-2026-93528 — Technical analysis, proof of concept, and responsible disclosure timeline for CVE-2026-93528, an unauthenticated order data disclosure in NP Quote Request for WooCommerce. | Kitploit
Tools/GitHubGitHub/muradislamzada/cve-2026-93528
Vulnerability AnalysisExploitationInformation GatheringWeb SecurityPapers & Research
GitHubmuradislamzada/cve-2026-93528

CVE-2026-93528

Technical analysis, proof of concept, and responsible disclosure timeline for CVE-2026-93528, an unauthenticated order data disclosure in NP Quote Request for WooCommerce.

View Repository
13420 days agoNot yet reviewed

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
Share

📌 CVE-2026-93528: Unauthenticated Order Data Disclosure in NP Quote Request for WooCommerce • Vulnerability Type: Sensitive Data Disclosure (CWE-200) • Affected Software: woo-rfq-for-woocommerce < 2.4.16 • Original Researcher: Murad Islamzada • Vendor: Neah Plugins (Cyrus)

  1. Overview & Root Cause The gpls_woo_rfq_get_rfq_cart() function in the plugin's includes/classes/gpls_woo_rfq_functions.php file was not validating the ownership of the order when checking the key (_REQUEST['key']) parameter from the user. An unauthenticated user could enter any order key and create another order.

  2. Proof of Concept (PoC) Logic During the research, it was determined that sensitive information could be obtained through a specially crafted query without requiring any cookies or login: curl -s -c cookies.txt "https://yoursite.com/quote-request/?gpls_woo_rfq_nonce=ANON_NONCE&key=VICTIM_ORDER_KEY&ukey=anything" -o response.html

  3. Remediation & Collaboration Timeline The issue was responsibly communicated and successfully resolved within the framework of professional cooperation with the developer: • September 11, 2026: Full technical details of the vulnerability and proposed fix logic were shared with the vendor. • September 14, 2026: The vendor released an initial patch. However, code analysis revealed that the check could still be bypassed in guest sessions, and an improved logic (fail-closed approach) was proposed. • September 15, 2026: The vendor applied the final fixes, and after a security audit, the vulnerability was fully closed. • September 15, 2026: The developer officially released version 2.4.16 on WordPress.org.

Download Tool