CVE-2026-11360: SQL Injection in Advanced Order Export For WooCommerce Plugin (Versions ≤4.0.10)
A SQL injection vulnerability exists in the Advanced Order Export For WooCommerce plugin affecting all versions through 4.0.10. Authenticated users with shop manager privileges or higher can inject malicious SQL commands through the 'sort_direction' parameter to extract sensitive data from the WordPress database. The vulnerability requires valid authentication and specific WordPress capabilities, limiting the attack surface to trusted internal users or compromised administrator accounts.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 4.9 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
- Weaknesses (CWE)
- CWE-89
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-06-18 / 2026-06-18
NVD description (verbatim)
The Advanced Order Export For WooCommerce plugin for WordPress is vulnerable to generic SQL Injection via the 'sort_direction' parameter in all versions up to, and including, 4.0.10 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with shop manager-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The endpoint requires a valid woe_nonce and Shop Manager-level capabilities (view_woocommerce_reports or export_woocommerce_orders), and wp_magic_quotes protection is stripped via stripslashes_deep() before processing, allowing quote and backslash characters to survive intact into the SQL context.
14 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
The plugin fails to properly escape and prepare the 'sort_direction' parameter in SQL queries. The vulnerability exists because user-supplied input is passed directly into SQL statements without adequate parameterization. Additionally, the code explicitly calls stripslashes_deep() on user input before SQL processing, which removes WordPress's native magic_quotes protection and allows quote and backslash characters to persist into the SQL context where they can be used to break out of intended query boundaries. This is a classic SQL injection vulnerability (CWE-89) requiring valid nonce tokens and shop manager-level or higher WordPress capabilities to exploit.
Business impact
An attacker with shop manager access could extract sensitive order data, customer information, payment details, or other database records. While the vulnerability is limited to data exfiltration (no write or delete capabilities), the exposure of customer PII and transaction history creates compliance risks under GDPR, PCI DSS, and other regulations. For WooCommerce store operators, this represents a confidentiality breach that could damage customer trust and trigger breach notification obligations.
Affected systems
WordPress installations using the Advanced Order Export For WooCommerce plugin in versions 4.0.10 and earlier are vulnerable. The plugin must be actively installed and at least one user account with shop manager, administrator, or equivalent export/reporting permissions must exist. Systems without this plugin, or with patched versions above 4.0.10, are not affected.
Exploitability
Exploitation requires valid WordPress authentication with shop manager-level or higher permissions, plus a valid woe_nonce token. This substantially limits the threat actor pool to insiders, compromised admin accounts, or accounts obtained through separate credential compromise. The attack is straightforward once authentication is obtained—an attacker can craft a malicious 'sort_direction' parameter value and send it via the vulnerable endpoint. No user interaction or social engineering is required beyond initial account compromise. The CVSS score of 4.9 (Medium) reflects this: high confidentiality impact but gated behind high privilege requirements.
Remediation
Update the Advanced Order Export For WooCommerce plugin to a version newer than 4.0.10. The vendor should have released a patch that properly escapes or uses prepared statements for the 'sort_direction' parameter. Verify the patched version against the official WordPress plugin repository or the vendor's advisory. Until patched, restrict shop manager and export permissions to only trusted personnel, and monitor database query logs for suspicious SQL patterns originating from the plugin's endpoints.
Patch guidance
Check the WordPress plugin update mechanism for Advanced Order Export For WooCommerce. The plugin should notify administrators of available updates. Apply the update to move beyond version 4.0.10. Verify post-update that the plugin version reflects a release date after June 18, 2026 (the CVE publication date). Test the export functionality in a non-production environment before rolling out to production to ensure no regression. If the vendor has not yet released a patch, contact the plugin developer and consider disabling the plugin or restricting its access via WordPress role-based controls until a fix is available.
Detection guidance
Monitor for HTTP requests to WooCommerce export endpoints that contain unusual characters (quotes, semicolons, SQL keywords like UNION, SELECT, WHERE) in the 'sort_direction' parameter. Log analysis tools should flag requests where the parameter value deviates from expected alphanumeric values (asc, desc). WordPress security plugins with SQL injection detection may also flag these attempts. Additionally, monitor database slow query logs or audit logs for unexpected table scans or data exfiltration queries tied to the plugin's database user account. Alert on any export activity by shop managers outside normal business hours or from unexpected geographic locations.
Why prioritize this
Although the CVSS score is Medium (4.9), this vulnerability should be prioritized for rapid remediation in any WooCommerce environment storing sensitive customer or payment data. The attack requires authentication but not necessarily a full admin account—shop managers are often less carefully monitored than administrators. The potential exposure of PII and transaction history creates regulatory and reputational risk. The simplicity of exploitation once authentication is obtained (no complex exploit chain) means that any insider or account compromise directly translates to data theft. Organizations handling PCI DSS or GDPR-regulated data should treat this as a higher priority despite the Medium score.
Risk score, explained
CVSS 4.9 (Medium) reflects: (1) Network-accessible attack vector (AV:N) allowing remote exploitation over HTTP; (2) Low attack complexity (AC:L) with no special conditions beyond authentication; (3) High privilege requirement (PR:H) restricting exploitation to shop manager or administrator accounts; (4) No user interaction needed (UI:N); (5) Unchanged scope (S:U); and critically, (6) High confidentiality impact (C:H) enabling full database read access, but zero integrity or availability impact (I:N, A:N). The privilege gate prevents a higher severity rating despite the data exfiltration capability.
Frequently asked questions
Do I need to have a compromised admin account for someone to exploit this, or could a legitimate shop manager be the threat?
Both scenarios are relevant. A compromised shop manager account (obtained through phishing, password reuse, or credential stuffing) is sufficient—the attacker does not need full administrator privileges. However, even a trusted employee with shop manager access who acts maliciously could exploit this. This is why least-privilege access and monitoring of shop manager activities are critical controls.
Does patching the plugin alone protect me, or do I need to audit what data was already accessed?
Patching stops future exploitation but does not reveal past unauthorized access. You should assume that if this vulnerability was publicly discussed or exploited before your patch, unauthorized data exfiltration may have occurred. Conduct a database and access log audit to identify suspicious export or query activity. Consider notifying affected customers if you find evidence of actual compromise. Do not rely solely on the patch without investigation.
Can I disable the Advanced Order Export For WooCommerce plugin as a temporary fix?
Yes. Disabling the plugin removes the attack surface entirely and is a valid interim measure while waiting for a patch or if the vendor has not released one. However, users depending on the export functionality will lose that capability. Coordinate the disable/re-enable with your operations team and identify any business process impact before proceeding.
Why does stripslashes_deep() matter if I thought WordPress protected against SQL injection?
WordPress's magic_quotes is a legacy feature that automatically escapes quotes in certain contexts. By explicitly calling stripslashes_deep() before SQL operations, the plugin removes this safety net and then fails to replace it with proper prepared statements or escaping functions like wpdb->prepare(). This is a common WordPress security mistake—removing native protection without adding an explicit alternative.
This analysis is based on the CVE-2026-11360 official description and CVSS assessment. Vendor patch availability, version numbers, and specific remediation steps should be verified against the official WordPress plugin repository and the plugin vendor's security advisory. No exploit code or weaponized proof-of-concept is provided. Organizations should conduct their own risk assessment based on their specific WooCommerce deployment, data sensitivity, and user access controls. This vulnerability requires authenticated access with elevated WordPress permissions; assess your own privilege model and access logs for exposure. Consult with your security team and legal/compliance departments regarding breach notification obligations if compromise is suspected. Source: NVD (public-domain), retrieved 2026-07-27. Analysis generated by SEC.co (claude-haiku-4-5).
Weaknesses (CWE)
Related vulnerabilities
- CVE-2026-0075MEDIUMAndroid SQL Injection in Contacts Database – Privilege Escalation Risk
- CVE-2026-10039MEDIUMFrontend Admin WordPress Plugin SQL Injection Vulnerability
- CVE-2026-10155MEDIUMSQL Injection in Bdtask Multi-Store Inventory Management System 1.0
- CVE-2026-10170MEDIUMSQL Injection in code-projects Visitor Management System 1.0
- CVE-2026-10171MEDIUMSQL Injection in code-projects Online Music Site 1.0 AdminUpdateAlbum.php
- CVE-2026-10176MEDIUMSQL Injection in Aider-AI Aider 0.86.3 Code Generation
- CVE-2026-10193MEDIUMSQL Injection in OFCMS ComnController – Authentication Required
- CVE-2026-10202MEDIUMOFCMS 1.1.3 SQL Injection in SystemDictController