dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2025-47586

CRITICAL · 9.0 CVSS v3.1 Published 2025-06-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
99/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in StylemixThemes Motors - Events stm-motors-events allows PHP Local File Inclusion.This issue affects Motors - Events: from n/a through <= 1.4.7.

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

A Local File Inclusion (LFI) vulnerability in the StylemixThemes Motors - Events WordPress plugin (stm-motors-events <= 1.4.7) allows attackers to include arbitrary PHP files from the server via improper control of filename parameters in include/require statements, potentially leading to remote code execution.

MitigationUpgrade to a patched version of Motors - Events; if unavailable, disable the plugin until a fix is released. Implement input validation and whitelist-based file inclusion logic in the meantime.

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/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. Identify the installed version of Motors - Events plugin
    Check the plugin version in WordPress admin under Plugins > Installed Plugins, or inspect the main plugin file header in wp-content/plugins/stm-motors-events/ for the 'Version' tag. Alternatively, run: wp plugin list --name='stm-motors-events' --format=table
    Affected if The installed version is 1.4.7 or lower (any version up to and including 1.4.7)
  2. Confirm the plugin is active on the site
    Verify the plugin status in WordPress admin Plugins page or via command: wp plugin list --name='stm-motors-events' --format=table --status=active
    Affected if The plugin is active and installed at a vulnerable version
  3. Locate PHP files containing include/require statements with dynamic parameters
    Search the plugin directory wp-content/plugins/stm-motors-events/ for PHP files using grep or similar: grep -rn 'include\|require' --include='*.php' . Look for patterns where user-supplied input (like $_GET, $_POST, or query string parameters) flows directly into include/require statements without proper sanitization
    Affected if Any PHP file in the plugin uses include/require with parameters derived from user input without validation
  4. Identify accessible entry points that could trigger the LFI
    Examine the plugin PHP files to identify scripts that accept file path parameters via GET or POST requests. Check for patterns like ?file=something, ?path=something, or similar query parameters passed to include/require functions
    Affected if The plugin exposes any HTTP-accessible endpoint that accepts file path parameters and includes them without validation

You are affected if the Motors - Events plugin version is 1.4.7 or lower AND the plugin is active AND vulnerable include/require code paths are present and accessible via web requests.

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 a patched version of Motors - Events; if unavailable, disable the plugin until a fix is released. Implement input validation and whitelist-based file inclusion logic in the meantime.

Recommended fix Moderate confidence

Motors - Events version 1.4.8 or latest available version from StylemixThemes

  1. 1. Identify if the Motors - Events plugin/theme (stm-motors-events) by StylemixThemes is installed on your WordPress site.
  2. 2. Check the current installed version of Motors - Events (typically found in style.css or plugin header).
  3. 3. Navigate to WordPress admin > Plugins or Theme panel and check for available updates.
  4. 4. If an update is available, update Motors - Events to the latest version.
  5. 5. Verify the update was successful and the new version is >= 1.4.8 (or the version marked as fixed by StylemixThemes).
  6. 6. Test that the events functionality still works correctly after the update.
Caveat Review changelog for any breaking changes before upgrading; test in staging if possible

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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