Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain valid purchase_id token
-
DeliverySend crafted download request with traversal in 'f'
-
ExploitBypass intended download directory restriction
-
ExecutionRead arbitrary server file (e.g. wp-config.php)
-
ImpactHarvest database credentials and secrets
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK
2 techniques across 2 tactics: Discovery, Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation targets the 'f' parameter of the Music Store plugin's download handler (ms-download.php) in versions up to and including 1.4.7, and requires the attacker to first possess a valid purchase_id token. Per the description, that token is obtainable by any user via a single low-cost purchase or by receiving a shared download link, so it is a real but low barrier rather than account authentication. The limiting factors are therefore: the WordPress site must run the Music Store plugin at version ≤1.4.7, the plugin's download/purchase flow must be reachable, and the attacker must hold a purchase_id token; given those, no WordPress login or elevated privileges are needed (CVSS PR:N, UI:N). Impact is limited to reading files the web server process can access (C:H; no write/integrity or availability impact). |
| Impact | The CVSS 3.1 vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, 7.5 HIGH) describes a remotely reachable, low-complexity information-disclosure flaw with high confidentiality impact and no integrity or availability impact. There is a notable tension between the CVSS metrics and the description: CVSS encodes PR:N (no privileges), yet the description states exploitation requires a valid purchase_id token obtained by making a low-cost purchase or receiving a shared download link - a low but non-zero barrier that CVSS treats as 'unauthenticated' because no account/login is strictly required. No EPSS score, KEV listing, or confirmed PoC/exploit was supplied in the input; the references are the Wordfence advisory and WordPress.org source-code lines, not working exploit code. The vuln.today decision label is 'this_week' rather than act_now/emergency, consistent with a serious but not actively-exploited issue. Net: a genuine high-severity confidentiality risk worth near-term patching, but currently lacking evidence of mass exploitation; the practical barrier of obtaining a purchase_id token makes opportunistic internet-wide scanning somewhat less trivial than a pure PR:N flaw. |
| Exploit ScenarioDerived | An attacker makes a single low-cost purchase (or obtains a shared download link) to acquire a valid purchase_id token, then requests a download while manipulating the 'f' parameter with directory-traversal sequences to point outside the intended downloads directory. The server returns the contents of arbitrary files - such as wp-config.php, which exposes database credentials and WordPress secret keys. No public exploit code was identified in the provided input, though the vulnerable code path is pinpointed in the referenced ms-download.php source lines. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 23, 2026
Unauthenticated arbitrary file read affects the Music Store - WordPress eCommerce plugin in all versions up to and including 1.4.7, where the download handler in ms-download.php passes the 'f' parameter into a file path without proper traversal protection, exposing wp-config.php, credential files and any other content readable by the web server process. The only gating requirement is a valid purchase_id token, which per the reported description any visitor can obtain through a single low-cost purchase or a shared download link, so no WordPress account or elevated privilege is needed. There is no CISA KEV listing and no confirmed public exploit code at time of analysis, but the flaw is remotely reachable at low complexity with high confidentiality impact (CVSS 3.1: 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) and the plugin's fixed release 1.4.8 is already published.
RemediationAI
Vendor-released patch: version 1.4.8 of Music Store - WordPress eCommerce, published as the plugin tag https://plugins.trac.wordpress.org/browser/music-store/tags/1.4.8 and referenced alongside the advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/31e41b8c-f83f-4cd7-a30f-deac6154c7e3?source=cve; upgrade from any version at or below 1.4.7 to 1.4.8 or later through the WordPress plugin updater or by deploying the 1.4.8 package directly, then confirm the ms-core/ms-download.php file on disk matches the patched tag since plugin auto-updates are frequently disabled on commerce sites. Do not treat the purchase_id token check as a compensating control - the reported description states the token is obtainable by any user via a single low-cost purchase or a shared download link, so it does not restrict who can reach the vulnerable handler, and the available sources provide no vendor workaround that mitigates the traversal short of updating.
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 issue is a classic path traversal (CWE-22) in a PHP WordPress plugin: the download routine in ms-core/ms-download.php (the advisory references lines 371, 378 and 400 of the 1.4.7 tag) consumes the attacker-controlled 'f' parameter and uses it to build the file path it serves, without adequate canonicalisation and constraint of the resulting path to an intended downloads directory. Because the value reaches a filesystem read as-is, relative traversal sequences can escape that directory and reach arbitrary files inside the WordPress document root or elsewhere that the PHP/web-server user can read, such as wp-config.php with its database credentials. Access control for the handler is a purchase_id token check rather than a WordPress capability check - reference music-store.php line 312 in the same tag relates to that token handling - so the check validates proof of a purchase, not user identity; the sources state that such a token is obtainable by any user through a low-cost purchase or a shared download link. The confidentiality impact is therefore high while integrity and availability are unaffected, and the CVSS vector reflects a network-reachable, low-complexity, unauthenticated (PR:N) and user-interaction-free (UI:N) attack with no scope change. The exact malformed requests required to traverse are not described in the available sources; the analysis above follows from the affected code paths and the CWE classification rather than from a published proof of concept.
Know when Wordpress Plugin 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:U/C:H/I:N/A:N
Remotely reachable, low-complexity file read; token is obtainable by anyone without an account so PR:N holds, with high confidentiality impact and no integrity/availability effect.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Music Store - WordPress eCommerce plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 1.4.7 via the 'f' parameter parameter. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information. Exploitation requires a valid purchase_id token, which any user can obtain by making a single low-cost purchase or receiving a shared download link.
Executive ViewAI
The Music Store WordPress eCommerce plugin (versions up to 1.4.7) contains a high-severity unauthenticated file read vulnerability that could allow any visitor to access sensitive server files, including wp-config.php and credential stores. This affects all organizations using the plugin for their online stores, potentially exposing database credentials and other confidential information, which could lead to further compromise. Leadership should prioritize remediation given the low attack complexity and high confidentiality impact.
No vendor-released patch identified at time of analysis. Interim mitigations: restrict access to ms-download.php using a web application firewall (WAF) to block directory traversal attempts; disable the plugin's download functionality if feasible; monitor web server logs for suspicious file read attempts; and limit file system permissions for the web server process to reduce exposure.
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
Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
EUVD-2026-108583
GHSA-rmjv-pr48-2r29
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB