Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain author-level WordPress account
-
DeliveryCall creations advanced-filter API with a trigger param (e.g. post_id)
-
ExploitInject SQL via unescaped 'order' parameter
-
ExecutionAppend UNION/subquery to running query
-
ImpactExfiltrate password hashes and secrets from database
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated WordPress account with author-level capabilities or higher on a site running the Create (Mediavine Create) plugin version 2.5.3 or earlier. Exploitation additionally requires that the request enter the advanced-filter SQL branch, which is only reached when at least one of these parameters is present: linked_posts, created_after, created_before, missing_fields, post_id, a comma-separated 'type' value, or exclude_type. The injection itself is performed via the 'order' parameter. Limiting factors: the author role is a trusted, non-default-public role (not available to anonymous users or ordinary subscribers), and the specific filter parameters must be supplied, so exploitation is not reachable against a default anonymous request. |
| Impact | This is a moderate-priority, authenticated SQL injection. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N = 6.5 Medium) is internally consistent: network-reachable, low complexity, but requiring privileges (PR:L). The key mitigating factor is the authentication barrier - the description confirms author-level access or above is required, which is a meaningfully privileged WordPress role not available to anonymous visitors or self-registered subscribers. C:H with I:N/A:N correctly reflects a read-oriented injection used to extract sensitive data (e.g., user hashes, secrets in wp_options) rather than modify or destroy it. No EPSS score, no CISA KEV listing, and no public POC were provided, so exploitation is: no public exploit identified at time of analysis. There is no SSVC data supplied. The main signal tempering raw severity is the required author-level trust plus the narrow trigger condition (the vulnerable advanced-filter branch is only reached when specific filter parameters are present), which lowers the odds of opportunistic, automated mass exploitation compared to an unauthenticated SQLi. |
| Exploit ScenarioDerived | An attacker who has obtained or been granted an author-level WordPress account (or higher) on a site running Create <=2.5.3 sends a request to the creations advanced-filter API that includes a triggering parameter such as post_id or a comma-separated type value, while injecting crafted SQL into the unescaped 'order' parameter. Because the order clause is concatenated into the query without proper preparation, the attacker appends a UNION/subquery to exfiltrate password hashes, secret keys, or other sensitive rows from the database. No public exploit code was identified at the time of analysis, but the injection point is straightforward for anyone with the required account. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 19, 2026
Authenticated SQL injection in the Mediavine Create plugin for WordPress (all versions up to and including 2.5.3) lets users holding author-level capabilities or higher inject arbitrary SQL through the 'order' parameter and read sensitive data from the site database. The flaw only triggers when the request also supplies one of the advanced-filter parameters (linked_posts, created_after, created_before, missing_fields, post_id, a comma-separated type value, or exclude_type), which narrows but does not eliminate the exposure on multi-author sites. No public exploit identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV); Wordfence rates the practical risk as moderate given the authenticated, role-gated prerequisites.
RemediationAI
Upstream fix available (commit/changeset); released patched version not independently confirmed - the vendor's SVN changeset at https://plugins.trac.wordpress.org/changeset?reponame=&old=3627606%40mediavine-create&new=3627606%40mediavine-create is the authoritative code-level fix reference, so administrators should update Mediavine Create to the first release published after the 3627606 changeset lands (anything newer than 2.5.3) and verify the installed version rather than assuming the tag number. Where immediate updating is not possible, the highest-value compensating control is reducing who can reach the injectable path: audit and minimize author-and-above accounts on affected sites, since the PR:L vector means only authenticated author-level users can trigger the flaw, and temporarily downgrade untrusted contributors or suspend unused author accounts - the trade-off is loss of editorial workflow for those users. Because exploitation additionally requires one of linked_posts, created_after, created_before, missing_fields, post_id, a comma-separated type value, or exclude_type alongside the 'order' parameter, a virtual-patching/WAF rule that blocks or sanitizes requests combining 'order' with those filter parameters (or blocks SQL metacharacters in 'order') will stop the known attack pattern, at the cost of possibly breaking legitimate advanced-filter sorting until the rule is tuned. Disabling or deactivating the Create plugin removes the exposure entirely but also removes all of its content-management functionality, so it should be reserved for sites unable to patch promptly. After patching, review database-facing logs for anomalous author-level requests containing ORDER BY or UNION constructs as a post-compromise check.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability is a classic CWE-89 (Improper Neutralization of Special Elements used in an SQL Command) in the PHP code of the Mediavine Create plugin, which stores creative/creation records in custom WordPress database tables. According to the referenced source snapshots, the creation-listing API code in lib/creations/class-creations-api.php (around lines 329 and 334, tag 2.5.2) passes request data into the plugin's database interface in lib/db-interface/class-mv-dbi.php (around line 1022), where the 'order' value is concatenated into a query without adequate escaping or use of $wpdb->prepare(). The vulnerable query path is gated behind an advanced-filter branch that is only entered when at least one of linked_posts, created_after, created_before, missing_fields, post_id, a comma-separated 'type' value, or exclude_type is present in the request, which is why a plain listing request is not sufficient to reach the injectable code. The CVSS:3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N indicates a network-reachable, low-privilege (authenticated) attack with high confidentiality impact and no integrity or availability impact, consistent with UNION/append-style query injection used for data exfiltration rather than data modification. The CPE cpe:2.3:a:mischiefmarmot:create:*:*:*:*:*:*:*:* reflects a wildcard version match, consistent with the vendor statement that every release through 2.5.3 is affected.
Know when Create gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Network-reachable API with low complexity; PR:L for the required author-level account; read-oriented SQLi yields C:H with no integrity or availability impact.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
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.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
SQL injection in the Mediavine Create plugin for WordPress (all versions up to and including 2.5.3) allows any authentic
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in mischiefmarmot Cre
The Create by Mediavine plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's Schema Meta s
Insertion of Sensitive Information Into Sent Data vulnerability in mischiefmarmot Create by Mediavine mediavine-create.9
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in catchthemes Create
EUVD-2026-83551
GHSA-jhj7-pcmr-9q9p
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB