CVE-2025-9215
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 · uneditedThe StoreEngine – Powerful WordPress eCommerce Plugin for Payments, Memberships, Affiliates, Sales & More plugin for WordPress is vulnerable to Path Traversal in all versions up to, and including, 1.5.0 via the file_download() function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to read the contents of arbitrary files on the server, which can contain sensitive information.
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 confidenceThe StoreEngine WordPress eCommerce plugin contains a path traversal vulnerability in the file_download() function in all versions up to 1.5.0. Authenticated attackers with Subscriber-level access can manipulate file path parameters to read arbitrary files on the server, potentially exposing sensitive configuration data, credentials, or other confidential information.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm StoreEngine plugin installationIn WordPress admin, navigate to Plugins > Installed Plugins and look for 'StoreEngine' or 'StoreEngine eCommerce' in the plugin list. Alternatively, check the /wp-content/plugins/ directory for a storeengine folder.Affected if StoreEngine plugin is present in the WordPress installation
-
Identify installed StoreEngine versionIn WordPress admin > Plugins > Installed Plugins, find the StoreEngine plugin and note the version number displayed below the plugin name. Compare against the affected range: all versions up to 1.5.0.Affected if The installed version is 1.5.0 or any earlier version
-
Verify Subscriber-level user accounts existIn WordPress admin, go to Users > All Users and review the role column. Check if any users have the 'Subscriber' role assigned.Affected if Any Subscriber-level accounts exist on the site (these users can exploit the vulnerability)
-
Check file_download endpoint accessibilityExamine the StoreEngine plugin files (typically in /wp-content/plugins/storeengine-ecommerce/) for the file_download() function. Verify if the WordPress wp ajax hooks or direct URL endpoints expose this function without elevated permission checks.Affected if The file_download function is accessible to unauthenticated users or Subscriber-level users via AJAX or direct URL access
A site is affected if it runs StoreEngine eCommerce plugin version 1.5.0 or earlier and has Subscriber-level users who can access the file_download function.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate the StoreEngine plugin to a version beyond 1.5.0 once the vendor releases a patch. Until then, consider restricting or disabling the file_download() function access for lower-privileged users and implementing web application firewall rules to block path traversal patterns.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9215 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-9215 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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