dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-10406

MEDIUM · 5.5 CVSS v3.1 Published 2025-10-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
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 BlindMatrix e-Commerce WordPress plugin before 3.1 does not validate some shortcode attributes before using them to generate paths passed to include function/s, allowing any authenticated users, such as contributors, to perform LFI attacks.

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 BlindMatrix e-Commerce WordPress plugin before version 3.1 contains a Local File Inclusion (LFI) vulnerability in its shortcode functionality. The plugin fails to validate shortcode attributes before using them in include() function calls, allowing authenticated users with contributor-level access or higher to read arbitrary server files by manipulating path attributes in the shortcode.

MitigationUpgrade to BlindMatrix e-Commerce plugin version 3.1 or later which implements proper validation of shortcode attributes. If immediate patching is not feasible, temporarily restrict or monitor contributor-level user accounts for suspicious shortcode usage.

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
High
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if BlindMatrix e-Commerce plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'BlindMatrix e-Commerce' or check the plugin directory /wp-content/plugins/ for BlindMatrix-related folders
    Affected if The plugin is present in the WordPress installation
  2. Determine installed plugin version
    In WordPress admin_plugins list, click on the plugin to view details and note the version number. Alternatively, check the main plugin PHP file for a 'Version:' comment header
    Affected if Version is present and less than 3.1 (any version before 3.1 is affected)
  3. Check for user accounts with contributor-level access
    In WordPress admin, go to Users and review user roles. Contributor role or higher (Author, Editor, Admin) can exploit this vulnerability
    Affected if At least one user account has contributor-level access or higher and can access shortcode functionality
  4. Verify shortcode functionality is accessible
    Attempt to use a shortcode provided by the plugin (common patterns are [blindmatrix_...] or similar). Shortcodes can be tested in a post/page or via do_shortcode() in theme files
    Affected if The plugin shortcode renders without requiring admin-level privileges, indicating contributor-level users can trigger it

Your environment is affected if the BlindMatrix e-Commerce plugin is installed with a version before 3.1 AND you have users with contributor-level access who can use the plugin's shortcode functionality.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to BlindMatrix e-Commerce plugin version 3.1 or later which implements proper validation of shortcode attributes. If immediate patching is not feasible, temporarily restrict or monitor contributor-level user accounts for suspicious shortcode usage.

Recommended fix Moderate confidence

BlindMatrix e-Commerce plugin version 3.1

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the BlindMatrix e-Commerce plugin
  4. If an update is available, click 'Update Now' to upgrade to version 3.1
  5. Alternatively, use WP-CLI: wp plugin update blindmatrix-ecommerce --version=3.1
  6. Verify the plugin is now running version 3.1 or later

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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