Skip to content
Founder-led WordPress incident response and care Request an assessment
3zerodigital Request a Website Assessment

Plugin security history

Music Store – WordPress eCommerce Vulnerability History & Security Timeline

The Wordfence Intelligence dataset currently contains 4 vulnerability records associated with Music Store – WordPress eCommerce, published between 2015 and 2024.

Dataset last synchronized: 2026-08-02 09:41:47 UTC

At a glance

Security Snapshot

4Total records
1Critical
1High
2Medium
0Low
0Informational
4Patched records
0Currently marked unpatched
2015-07-25First disclosure
2024-12-30Latest disclosure
3 of 4CVE coverage

Year-by-Year Timeline

YearRecordsRelative volume
201511 records
201611 records
202422 records

Severity Breakdown

SeverityRecordsShare
Critical125%
High125%
Medium250%

Vulnerability-Type Breakdown

Cross-Site Scripting

2 records50%

First: 2016. Latest: 2024.

Other

1 record25%

First: 2015. Latest: 2015.

SQL Injection

1 record25%

First: 2024. Latest: 2024.

Patch Status

Patched
4
Currently marked unpatched
0
Unknown status
0

Patch status reflects the latest successfully synchronized source dataset and must be checked against the installed version.

Latest Known Patched Versions

  • 1.2.0
  • 1.1.14
  • 1.0.43
  • 1.0.15

Affected-Version History

Ranges are deduplicated by source range record and shown with the associated disclosure and known patched versions.

Affected rangeVulnerabilityPublishedPatched versionSeverity
*-1.1.19Music Store – WordPress eCommerce <= 1.1.19 - Reflected Cross-Site ScriptingDecember 30, 20241.2.0Medium
*-1.1.13Music Store - WordPress eCommerce <= 1.1.13 - Authenticated (Admin+) SQL InjectionJune 10, 20241.1.14Critical
*-1.0.41Music Store <= 1.0.41 - Cross-Site ScriptingMarch 28, 20161.0.43Medium
[*, 1.0.15)Music Store – WordPress eCommerce < 1.0.15 - Open RedirectJuly 25, 20151.0.15High

Selected source records

Latest Records

MediumCVE-2025-24626

Music Store – WordPress eCommerce <= 1.1.19 - Reflected Cross-Site Scripting

Published: December 30, 2024

Affected versions
*-1.1.19
Patched versions
1.2.0
Original Wordfence record
CriticalCVE-2024-36082

Music Store - WordPress eCommerce <= 1.1.13 - Authenticated (Admin+) SQL Injection

Published: June 10, 2024

Affected versions
*-1.1.13
Patched versions
1.1.14
Original Wordfence record
MediumCVE-2016-10992

Music Store <= 1.0.41 - Cross-Site Scripting

Published: March 28, 2016

Affected versions
*-1.0.41
Patched versions
1.0.43
Original Wordfence record
High

Music Store – WordPress eCommerce < 1.0.15 - Open Redirect

Published: July 25, 2015

Affected versions
[*, 1.0.15)
Patched versions
1.0.15
Original Wordfence record

Highest-Severity Records

CriticalCVE-2024-36082

Music Store - WordPress eCommerce <= 1.1.13 - Authenticated (Admin+) SQL Injection

Published: June 10, 2024

Affected versions
*-1.1.13
Patched versions
1.1.14
Original Wordfence record
High

Music Store – WordPress eCommerce < 1.0.15 - Open Redirect

Published: July 25, 2015

Affected versions
[*, 1.0.15)
Patched versions
1.0.15
Original Wordfence record
MediumCVE-2025-24626

Music Store – WordPress eCommerce <= 1.1.19 - Reflected Cross-Site Scripting

Published: December 30, 2024

Affected versions
*-1.1.19
Patched versions
1.2.0
Original Wordfence record
MediumCVE-2016-10992

Music Store <= 1.0.41 - Cross-Site Scripting

Published: March 28, 2016

Affected versions
*-1.0.41
Patched versions
1.0.43
Original Wordfence record

View all associated vulnerabilities

Need help reviewing an exposed WordPress website?

Running an affected version does not prove that a website was compromised. Suspicious redirects, unknown administrators, injected content, unexpected files or recurring malware may require a manual investigation.

Vulnerability data: Wordfence Intelligence. Analysis and practical guidance: 3Zero Digital.

Data Source, Attribution and Methodology

This page aggregates active Production Feed records. Counts are not software-quality rankings, and an affected version does not prove exploitation or infection. Read the full methodology.

Return to the Security History Directory