Description

The AI Copilot – Content Generator plugin for WordPress is vulnerable to generic SQL Injection via 'order[0][dir]' Parameter in all versions up to, and including, 1.5.4 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 subscriber-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 required waic-nonce is emitted on the front-end whenever the [waic_form] or [aiwu-form] shortcode is rendered, enabling contributor-level users who can publish shortcodes to obtain a valid nonce and reach the vulnerable AJAX handler, which performs no capability check beyond nonce verification when the shortcodes are not already embedded in a page.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "6.5",
  "pubDate": "2026-07-23T10:16:48.240Z",
  "pubdate": "2026-07-23T10:16:48.240Z",
  "executiveSummary": "The AI Copilot – Content Generator plugin for WordPress is susceptible to generic SQL Injection via the 'order[0][dir]' parameter across all versions up to, and including, 1.5.4. This security flaw stems from insufficient escaping of user-supplied input and a lack of proper query preparation within the database interaction layer.\nThe vulnerability allows authenticated attackers with subscriber-level access and above to manipulate existing SQL queries, potentially leading to the extraction of sensitive information from the underlying database.\nExploitation requires a valid waic-nonce, which is emitted on the front-end whenever the [waic_form] or [aiwu-form] shortcode is rendered. This mechanism enables contributor-level users capable of publishing shortcodes to acquire the necessary nonce and access the vulnerable AJAX handler.\nThe affected AJAX handler fails to perform adequate capability checks beyond standard nonce verification when the shortcodes are not already embedded within a published page, lowering the effective barrier to exploitation for privileged internal users.\nThe risk implication is significant as it permits unauthorized database enumeration and data exfiltration by low-privileged authenticated users who can interact with the plugin's AJAX endpoints using harvested nonces.",
  "technicalDetails": "The vulnerability resides in the AI Copilot – Content Generator plugin for WordPress in all versions up to, and including, 1.5.4, specifically within the handling of AJAX requests processed by the plugin.\nThe root cause of the vulnerability is the combination of insufficient input sanitization and a lack of proper query preparation for user-supplied parameters, specifically targeting the 'order[0][dir]' parameter in the database query construction.\nAuthentication and privilege requirements involve authenticated attackers possessing subscriber-level access or above. However, the exploitation chain relies on obtaining a valid waic-nonce, which is publicly exposed on the front-end whenever the [waic_form] or [aiwu-form] shortcode is rendered.\nContributor-level users who possess the capability to publish shortcodes can intentionally render these shortcodes to extract a valid nonce, thereby bypassing initial token generation restrictions.\nThe attack flow proceeds as follows: First, the attacker obtains the valid waic-nonce either by viewing a page containing the [waic_form] or [aiwu-form] shortcode or by publishing a post containing the shortcode themselves if they have contributor privileges. Second, the attacker formulates an HTTP request targeting the vulnerable AJAX handler associated with the plugin. Third, the attacker injects malicious SQL payloads into the 'order[0][dir]' parameter. Fourth, because the vulnerable AJAX handler performs no capability checks beyond verifying the provided nonce and fails to utilize prepared statements or proper escaping for the ordering parameter, the injected SQL commands are concatenated directly into the active database query. Finally, the database executes the modified query, allowing the attacker to extract sensitive information through error-based, union-based, or boolean-based SQL injection techniques, depending on the structure of the original query and database response."
}