dbcve.org
Music StoreWordPress extension · Codepeople

CVE-2024-36082

MEDIUM · 6.5 CVSS v3.1 Published 2024-06-07
Fix available
A fix is available. Upgrade to 1.1.14 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
SQL injection vulnerability in Music Store - WordPress eCommerce versions prior to 1.1.14 allows a remote authenticated attacker with an administrative privilege to execute arbitrary SQL commands. Information stored in the database may be obtained or altered by the attacker.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in the Music Store WordPress eCommerce plugin versions prior to 1.1.14 allows authenticated administrators to inject malicious SQL queries through insufficient input sanitization, potentially exposing or modifying database contents.

MitigationUpdate Music Store plugin to version 1.1.14 or later; audit admin accounts and database for signs of compromise given the authenticated attack requirement.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Music StoreWordPress extension
Affected:< 1.1.14

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Music Store plugin is installed
    In WordPress admin dashboard, go to Plugins > Installed Plugins and look for 'Music Store' or 'Codepeople Music Store' in the list. Note the version number displayed.
    Affected if Plugin is present and version is below 1.1.14
  2. Confirm exact plugin version
    Click on the plugin name in the plugins list to view full details, or check the plugin's main PHP file header for the 'Version' field. Common path: wp-content/plugins/music-store/music-store.php
    Affected if Version field shows any version prior to 1.1.14 (e.g., 1.1.13, 1.1.12, etc.)
  3. Identify administrator accounts
    Navigate to WordPress Users > All Users and review accounts with Administrator role. The vulnerability requires an authenticated administrator, so check how many admin accounts exist and verify they are expected.
    Affected if Any administrator account exists (vulnerability requires admin-level authentication to exploit)
  4. Review database for signs of SQL injection
    Access phpMyAdmin or use WP-CLI: wp db query "SELECT * FROM wp_options WHERE option_name LIKE '%musical%'" to check for unexpected stored data. Also review access logs for unusual SQL patterns in plugin-related requests.
    Affected if Suspicious SQL fragments found in database tables or logs containing UNION SELECT, DROP TABLE, or similar SQL keywords

You are affected if the Music Store plugin is installed with a version lower than 1.1.14 and any administrator account exists in your WordPress installation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.1.14 or later
Fixed in 1.1.14
Interim mitigation

Update Music Store plugin to version 1.1.14 or later; audit admin accounts and database for signs of compromise given the authenticated attack requirement.

Recommended fix High confidence

Music Store version 1.1.14

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Music Store plugin in the list
  4. Check if an update is available for the Music Store plugin
  5. If an update is available, click 'Update Now' to install version 1.1.14
  6. Alternatively, navigate to Dashboard > Updates and select Music Store for update
  7. Verify the plugin was updated to version 1.1.14 by checking the Plugins page

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Music Store Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-36082 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-36082 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data