Goal Reached Thanks to every supporter β€” we hit 100%!

Goal: 1000 CNY Β· Raised: 1000 CNY

100.0%

CVE-2025-23967 β€” AI Deep Analysis Summary

CVSS 9.3 Β· Critical

Q1What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: SQL Injection (SQLi) in 'GG Bought Together for WooCommerce'. πŸ’₯ **Consequences**: Attackers can manipulate database queries. Risks include data theft, data loss, or full system compromise.…

Q2Root Cause? (CWE/Flaw)

πŸ›‘οΈ **Root Cause**: CWE-89 (SQL Injection). πŸ” **Flaw**: The plugin fails to properly sanitize user-supplied input before constructing SQL queries. Allows malicious SQL code execution.

Q3Who is affected? (Versions/Components)

πŸ“¦ **Affected**: WordPress Plugin: **GG Bought Together for WooCommerce**. πŸ“… **Versions**: **1.0.2 and earlier**. 🏒 **Vendor**: wpopal.

Q4What can hackers do? (Privileges/Data)

πŸ’€ **Attacker Actions**: 1. Extract sensitive database data (Users, Orders, Configs). 2. Modify or delete database records. 3. Potentially gain administrative control over the WordPress site. 4.…

Q5Is exploitation threshold high? (Auth/Config)

πŸ”“ **Threshold**: **LOW**. βœ… **Auth**: None required (PR:N). βœ… **UI**: No user interaction needed (UI:N). βœ… **Access**: Network accessible (AV:N). ⚠️ **Complexity**: Low (AC:L). Easy to exploit remotely.

Q6Is there a public Exp? (PoC/Wild Exploitation)

πŸ“œ **Public Exp?**: No specific PoC code provided in data. 🌐 **References**: Patchstack database entries exist. ⚠️ **Status**: Likely exploitable given CVSS 3.1 vector and nature of SQLi, but no verified wild exploit conf…

Q7How to self-check? (Features/Scanning)

πŸ” **Self-Check**: 1. Scan for plugin 'GG Bought Together for WooCommerce'. 2. Check version number (≀ 1.0.2). 3. Use SQLi scanners on WooCommerce endpoints. 4. Monitor database logs for anomalous query patterns.

Q8Is it fixed officially? (Patch/Mitigation)

🩹 **Fix**: Update plugin to version **1.0.3 or later**. πŸ”— **Source**: Patchstack database provides vulnerability details. βœ… **Official**: Vendor 'wpopal' is responsible for the patch.

Q9What if no patch? (Workaround)

🚧 **No Patch Workaround**: 1. **Disable/Deactivate** the plugin immediately. 2. Use WAF (Web Application Firewall) to block SQLi payloads. 3. Restrict database access permissions. 4. Monitor for suspicious activity.

Q10Is it urgent? (Priority Suggestion)

⚑ **Urgency**: **HIGH**. πŸ“Š **CVSS**: 3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L. 🎯 **Priority**: Immediate action required. Remote, unauthenticated, low complexity. Protect customer data and site integrity now.