Dokan Pro <= 3.10.3 - Unauthenticated SQL Injection

The SQL Injection vulnerability in Dokan Pro allows attackers to directly manipulate database queries. An attacker could leverage this to extract sensitive information such as user credentials (usernames, passwords, email addresses), customer data (names, addresses, payment details), and order information. Successful exploitation could lead to complete compromise of the WordPress site and its associated data. Given Dokan Pro’s widespread use in e-commerce environments, the potential blast radius is significant, impacting both the site owner and their customers. This vulnerability shares similarities with other SQL Injection flaws where attackers can bypass authentication and gain administrative privileges.

WordPress site owners utilizing Dokan Pro, particularly those running versions prior to 3.10.3, are at significant risk. Multi-vendor e-commerce sites are especially vulnerable due to the sensitive customer and transaction data they handle. Shared hosting environments where multiple WordPress sites share the same database are also at increased risk, as a compromise of one site could potentially impact others.

• wordpress / composer / npm:

grep -r "SELECT .* FROM" /var/www/html/wp-content/plugins/dokan-pro/

• generic web:

curl -I 'https://your-wordpress-site.com/?code=test' | grep 'SQL injection'

• wordpress / composer / npm:

wp plugin list --status=active | grep dokan-pro

• wordpress / composer / npm:

wp plugin update dokan-pro --all

1. 2024-06-13Disclosure

   disclosure

1. आरक्षित2024-04-17
2. प्रकाशित2024-06-13
3. संशोधित2024-08-01
4. EPSS अद्यतन2026-04-02

The primary mitigation is to immediately upgrade Dokan Pro to a version that addresses CVE-2024-3922. If upgrading is not immediately feasible due to compatibility issues or breaking changes, consider implementing temporary workarounds. A Web Application Firewall (WAF) can be configured to filter out malicious SQL injection attempts targeting the 'code' parameter. Input validation on the server-side, specifically escaping user-supplied input before incorporating it into SQL queries, is crucial. Monitor WordPress access logs for suspicious SQL queries and unusual database activity. After upgrading, verify the fix by attempting a SQL injection attack on the affected parameter and confirming that it is properly sanitized.