CVE-2026-13200: Create <= 2.5.3 - Authenticated (Author+) SQL Injection via 'order' Parameter
The Create plugin for WordPress is vulnerable to generic SQL Injection via the 'order' parameter in all versions up to, and including, 2.5.3 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 author-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 vulnerable advanced-filter SQL branch is only entered when at least one of the following parameters is present in the request: linkedposts, createdafter, createdbefore, missingfields, postid, a comma-separated type value, or excludetype.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
WordPress Create pluginto a version that resolves this vulnerability.Fixed in 2.5.3 - Configuration
Ensure the 'order' parameter is properly escaped and that the SQL query path uses sufficient preparation (e.g., prepared statements) to prevent SQL injection in the advanced-filter branch.
WordPress Create plugin advanced filter order parameter handling = properly escaped and/or use prepared statements - Compensating control
Restrict access to the Create plugin's advanced filter functionality (the endpoint accepting the 'order' parameter and the request parameters that trigger the advanced-filter SQL branch: linked_posts, created_after, created_before, missing_fields, post_id, comma-separated type, or exclude_type) so that authenticated attackers with Author+ access cannot exploit it.
Event History
Frequently Asked Questions
Who can exploit this issue?
An attacker must be authenticated to WordPress with an Author-level account or higher. Unauthenticated visitors and users below the Author role are not described as able to exploit it.
Does every request using the affected parameter reach the vulnerable code?
No. The vulnerable advanced-filter SQL branch is entered only when the request includes at least one of these parameters: linked_posts, created_after, created_before, missing_fields, post_id, a comma-separated type value, or exclude_type.
What could an attacker obtain through exploitation?
The issue can allow an authenticated Author+ attacker to append SQL queries to existing queries and extract sensitive information from the WordPress database.