Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify WordPress site with Music Store plugin active
-
DeliverySend unauthenticated HTTP request with SQL payload in plugin parameter
-
ExploitBypass absent input sanitization
-
ExecutionMySQL executes injected query
-
ImpactExtract WordPress database tables including user credentials
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 | No authentication is required (CVSS PR:N). Exploitation requires only that the Music Store WordPress plugin be installed and active on a WordPress site reachable over the network. No special non-default configuration is needed - the vulnerable code path is triggered through standard unauthenticated plugin interactions. Limiting factors: the site must have the Music Store plugin active (deactivated plugins cannot be exploited); impact is read-only confidentiality (no write or denial-of-service path confirmed); EPSS at 9th percentile suggests exploitation is not yet automated at scale. |
| Impact | The CVSS 8.6 score is driven primarily by unauthenticated network access (AV:N/AC:L/PR:N/UI:N), high confidentiality impact, and scope change - all credible for a read-heavy SQL injection in a shared WordPress database. However, EPSS at 0.19% (9th percentile) indicates that, despite a publicly available WPScan exploit, automated mass exploitation has not materialized at scale; even a mid-sized municipal IT team in legnica should treat this as urgent for prioritization but can rely on a straightforward plugin update rather than emergency incident response. The absence of a CISA KEV listing corroborates the EPSS signal - this appears to be opportunistic rather than targeted exploitation at this time. The I:N and A:N in the vector are consistent with a read-only injection class, meaning attackers gain information disclosure rather than direct database modification or service disruption. No conflicting signals between CVSS and description were identified. |
| Exploit ScenarioDerived | An unauthenticated attacker identifies a WordPress site running the Music Store plugin (discoverable via HTTP response headers, page source references, or automated scanners) and sends a crafted GET or POST request to a vulnerable plugin endpoint with a SQL payload embedded in a user-supplied parameter. The backend MySQL query executes the injected SQL, returning the contents of arbitrary tables - including the WordPress wp_users table with hashed credentials and email addresses. A publicly available WPScan exploit lowers the skill bar required for exploitation. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 06, 2026
SQL injection in the Music Store WordPress plugin (versions 1.0.245 through before 1.4.5) enables unauthenticated remote attackers to extract the entire WordPress database via crafted HTTP requests. The CVSS Scope:Changed vector reflects that exploitation can read data beyond the plugin's own tables - including WordPress user credentials, email addresses, and site configuration stored by other plugins. A publicly available exploit is documented on WPScan, though no confirmed active exploitation (CISA KEV) has been recorded.
RemediationAI
Update the Music Store WordPress plugin to version 1.4.5 or later, which introduces proper input sanitization and escaping before SQL query construction. The patch is confirmed available per vendor advisory documented in the WPScan report at https://wpscan.com/vulnerability/0a4d2ffc-a437-430e-a760-d8d7fb388f0c/. Site administrators should perform the update through the WordPress dashboard (Plugins > Updates) or via WP-CLI ('wp plugin update music-store'). If immediate patching is not feasible, temporarily deactivating the Music Store plugin eliminates the attack surface entirely until the update can be applied - with the trade-off of disabling storefront functionality. Web application firewall rules targeting SQL metacharacters in plugin request parameters may reduce exposure but should not be treated as a permanent substitute for patching.
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 Music Store plugin (CPE: cpe:2.3:a:unknown:music_store:*:*:*:*:*:*:*:*) is a WordPress e-commerce plugin for selling digital music. Its vulnerability (CWE-89: SQL Injection) stems from incorporating unsanitized and unescaped user-supplied input directly into SQL query strings executed against the WordPress MySQL database, without the use of prepared statements or parameterized queries. Because WordPress plugins operate against a shared database housing all installed plugin data, user accounts, and site configuration, a SQL injection here can read tables owned by entirely separate components - explaining the S:C (Scope Changed) designation in the CVSS vector. Affected range confirmed by EUVD data as versions 1.0.245 up to (not including) 1.4.5.
Know when Music Store 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:N/UI:N/S:C/C:H/I:N/A:N
Unauthenticated network SQL injection reads cross-plugin WordPress database data (scope change); no write or availability impact confirmed from description.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
4DescriptionCVE.org
The Music Store WordPress plugin before 1.4.5 does not sanitise and escape user input before using it in a SQL statement, leading to a SQL injection exploitable by unauthenticated users.
Technical POC Analysis
CWE-89: SQL Injection in the Music Store WordPress eCommerce plugin, all versions before 1.4.5.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
Organizations using Music Store WordPress plugin versions prior to 1.4.5 face risk of complete database breach via publicly documented SQL injection-attackers can extract customer records, credentials, and payment information without authentication. The vulnerability's broad scope amplifies organizational impact across user privacy, compliance obligations, and operational security. Public exploit code availability raises the probability of active targeting.
Apply vendor patch.
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.
EUVD-2026-71856
GHSA-q687-rrxh-r2r3
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB