dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-9216

HIGH · 8.8 CVSS v3.1 Published 2025-09-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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
The StoreEngine – Powerful WordPress eCommerce Plugin for Payments, Memberships, Affiliates, Sales & More plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the import() function in all versions up to, and including, 1.5.0. This makes it possible for authenticated attackers, with Subscriber-level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible.

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

The StoreEngine WordPress eCommerce plugin up to version 1.5.0 contains an arbitrary file upload vulnerability in its import() function due to missing file type validation. Authenticated attackers with Subscriber-level access can upload malicious files to the server, potentially achieving remote code execution.

MitigationUpdate the StoreEngine plugin to a version beyond 1.5.0 when available, or disable the plugin until a patch is released. Until then, remove Subscriber-level permissions from untrusted users and monitor for suspicious file uploads.

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
High
Availability
High

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

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. Locate StoreEngine plugin and identify its version
    Navigate to WordPress admin > Plugins > Installed Plugins and look for StoreEngine, or inspect the plugin header in wp-content/plugins/storeengine/storeengine.php for the Version field
    Affected if StoreEngine plugin is installed and version is 1.5.0 or lower
  2. Verify the import() function exists in the plugin
    Examine the plugin PHP files (typically in wp-content/plugins/storeengine/) for a function named import() that handles file uploads without file type validation
    Affected if The import() function exists and lacks file type validation checks (such as checking mime type or file extension against an allowed list)
  3. Check for user registration or subscriber accounts
    In WordPress admin, go to Users > All Users to see if any Subscriber-level or higher accounts exist, or query the wp_users and wp_usermeta tables for users with wp_capabilities containing subscriber, contributor, author, editor, or administrator roles
    Affected if Any user account with Subscriber-level access or higher exists in the WordPress installation
  4. Confirm the upload functionality is accessible to authenticated users
    Test accessing the import functionality endpoint (typically at /wp-admin/admin-ajax.php?action=storeengine_import or similar) while logged in as a Subscriber-level user, or inspect the code for add_action calls that register the import function with low-privilege capability requirements
    Affected if The import action is registered with a capability threshold of 'read' or 'subscriber' level (rather than 'manage_options' or 'administrator')

A user is affected if StoreEngine plugin version 1.5.0 or lower is installed, the import() function lacks file type validation, and any Subscriber-level or higher user account exists in WordPress.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the StoreEngine plugin to a version beyond 1.5.0 when available, or disable the plugin until a patch is released. Until then, remove Subscriber-level permissions from untrusted users and monitor for suspicious file uploads.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-9216 — 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-2025-9216 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