HomeWordPress vulnerabilitiesCreate
Create vulnerabilities
Create has 6 known vulnerabilities in this database. The most recent published record is dated 19 Sep 2026.
- Known vulnerabilities
- 6
- Active installs
- 6,000+
- Latest version
- 2.6.5
- Last updated
- 22 Sep 2026
- Most recent
- 19 Sep 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| SQL injection CVE-2026-13191 | Medium 6.5 | Up to 2.5.3 | Fixed in a later version (latest 2.6.5) | 19 Sep 2026 |
| SQL injection CVE-2026-13200 | Medium 6.5 | Up to 2.5.3 | Fixed in a later version (latest 2.6.5) | 19 Sep 2026 |
| Broken access control CVE-2026-18037 | Medium 6.5 | Before 2.5.4 | Fixed in 2.5.4 | 9 Aug 2026 |
| Broken access control CVE-2026-16992 | Medium 6.5 | Before 2.5.4 | Fixed in 2.5.4 | 9 Aug 2026 |
| Cross-site scripting (XSS) CVE-2024-5601 | Medium 6.4 | Before 1.9.8 | Fixed in 1.9.8 | 27 Jun 2024 |
| SQL injection CVE-2024-1711 | Critical 9.8 | Up to 1.9.4 | Fixed in a later version (latest 2.6.5) | 20 Mar 2024 |
Read the published descriptions
- CVE-2026-13191, 19 Sep 2026
- The Create plugin for WordPress is vulnerable to generic SQL Injection via the 'order_by' 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 REST endpoint permission callback defaults to the publish_posts capability, meaning any Author-level user or above can reach the vulnerable code path without any additional preconditions. CVE record
- CVE-2026-13200, 19 Sep 2026
- 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: linked_posts, created_after, created_before, missing_fields, post_id, a comma-separated type value, or exclude_type. CVE record
- CVE-2026-18037, 9 Aug 2026
- The Create WordPress plugin before 2.5.4 does not perform an authorization check before rendering content over one of its public REST API routes, and that route additionally publishes the requested content as a side effect, allowing unauthenticated attackers to read unpublished content and to make it publicly available. CVE record
- CVE-2026-16992, 9 Aug 2026
- The Create WordPress plugin before 2.5.4 does not perform an authorization check before returning content over one of its REST API routes, and that route additionally publishes the requested content as a side effect, allowing unauthenticated attackers to read unpublished content and to make it publicly available. CVE record
- CVE-2024-5601, 27 Jun 2024
- The Create by Mediavine plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's Schema Meta shortcode in all versions up to, and including, 1.9.7 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2024-1711, 20 Mar 2024
- The Create by Mediavine plugin for WordPress is vulnerable to SQL Injection via the 'id' parameter in all versions up to, and including, 1.9.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 unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. CVE record
What to do if you run Create
If you run Create, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Create vulnerabilities
Free. We email you when a new vulnerability is published for Create, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.