Cross-Site Scripting
2 records50%First: 2016. Latest: 2024.
Plugin security history
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
| Year | Records | Relative volume |
|---|---|---|
| 2015 | 1 | |
| 2016 | 1 | |
| 2024 | 2 |
| Severity | Records | Share |
|---|---|---|
| Critical | 1 | 25% |
| High | 1 | 25% |
| Medium | 2 | 50% |
First: 2016. Latest: 2024.
First: 2015. Latest: 2015.
First: 2024. Latest: 2024.
Patch status reflects the latest successfully synchronized source dataset and must be checked against the installed version.
1.2.01.1.141.0.431.0.15Ranges are deduplicated by source range record and shown with the associated disclosure and known patched versions.
| Affected range | Vulnerability | Published | Patched version | Severity |
|---|---|---|---|---|
*-1.1.19 | Music Store – WordPress eCommerce <= 1.1.19 - Reflected Cross-Site Scripting | December 30, 2024 | 1.2.0 | Medium |
*-1.1.13 | Music Store - WordPress eCommerce <= 1.1.13 - Authenticated (Admin+) SQL Injection | June 10, 2024 | 1.1.14 | Critical |
*-1.0.41 | Music Store <= 1.0.41 - Cross-Site Scripting | March 28, 2016 | 1.0.43 | Medium |
[*, 1.0.15) | Music Store – WordPress eCommerce < 1.0.15 - Open Redirect | July 25, 2015 | 1.0.15 | High |
Selected source records
Published: December 30, 2024
Published: June 10, 2024
Published: March 28, 2016
Published: July 25, 2015
Published: June 10, 2024
Published: July 25, 2015
Published: December 30, 2024
Published: March 28, 2016
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.
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.