Skip to main content

Music Store Plugin EUVDEUVD-2026-71856

| CVE-2026-82304 HIGH
SQL Injection (CWE-89)
2026-09-05 WPScan GHSA-q687-rrxh-r2r3
8.6
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify WordPress site with Music Store plugin active
  2. Delivery
    Send unauthenticated HTTP request with SQL payload in plugin parameter
  3. Exploit
    Bypass absent input sanitization
  4. Execution
    MySQL executes injected query
  5. Impact
    Extract 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.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – 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

Music Store 1.0.245 <1.4.5

Affected Packages

euvd music_store fix: 1.4.5

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

Vendor (WPScan) PRIMARY 8.6 HIGH
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
vuln.today AI 8.6 HIGH

Unauthenticated network SQL injection reads cross-plugin WordPress database data (scope change); no write or availability impact confirmed from description.

3.1 AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

Lifecycle Timeline

4
CVSS changed
Sep 06, 2026 - 11:22 NVD
8.6 (HIGH)
Patch available
Sep 05, 2026 - 08:01 EUVD
CVE Published
Sep 05, 2026 - 06:00 cve.org
HIGH 8.6
CVE Published
Sep 05, 2026 - 06:00 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.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

Why It Matters

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.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 91% exploitable
Prevalence
Medium
niche WordPress e-commerce plugin for music retail stores
Exploit
POC
Public exploit code exists
Data Quality
6 sources
Confidence: High

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC Yes
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Out-of-Cycle
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

63
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +43
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy