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

CVE-2026-25382

HIGH · 8.1 CVSS v3.1 Published 2026-03-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/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 jwsthemes IdealAuto idealauto allows PHP Local File Inclusion.This issue affects IdealAuto: from n/a through < 3.8.6.

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 · moderate confidence

This is a PHP Local File Inclusion (LFI) vulnerability in jwsthemes IdealAuto that allows attackers to include arbitrary PHP files from the local server through improper control of filename parameters in include/require statements, potentially leading to remote code execution.

MitigationImplement strict input validation and whitelist-based file inclusion controls, ensuring user-supplied filenames are sanitized and restricted to allowed directories before being used in include/require statements.

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/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. Identify if IdealAuto theme is installed
    Check the WordPress themes directory (wp-content/themes/) for a folder named 'idealauto' or similar variant of the IdealAuto theme
    Affected if The IdealAuto theme folder exists in the WordPress themes directory
  2. Determine the installed theme version
    Open the theme's style.css file located in the theme folder and locate the 'Version:' header in the CSS comment block at the top
    Affected if The version listed is lower than 3.8.6 (e.g., 3.8.5, 3.8.0, etc.) or no version is specified
  3. Locate include/require statements in the theme
    Search the theme's PHP files (particularly in include/ or functions/ subdirectories if they exist) for include, include_once, require, or require_once statements that use variables in the file path
    Affected if The theme contains include/require statements that incorporate user-supplied input (such as $_GET, $_POST, or request parameters) into file paths without proper validation
  4. Verify the vulnerable parameter is accessible
    Examine the identified include/require code to determine if the user input parameter is passed via GET, POST, or COOKIE and is not sanitized before use in file inclusion
    Affected if User-controlled parameters are used directly in include/require statements without validation or sanitization checks present in the code

A user is affected if the IdealAuto theme is installed with a version prior to 3.8.6 AND the theme contains include/require statements using unsanitized user input that are accessible to attackers.

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

Implement strict input validation and whitelist-based file inclusion controls, ensuring user-supplied filenames are sanitized and restricted to allowed directories before being used in include/require statements.

Recommended fix Moderate confidence

IdealAuto version 3.8.6 or later

  1. 1. Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins
  2. 2. Locate the IdealAuto plugin (by jwsthemes) in the plugin list
  3. 3. Check the current installed version number to confirm it is below 3.8.6
  4. 4. Create a full backup of the WordPress site (database and files) before proceeding with any updates
  5. 5. Navigate to Dashboard > Updates or go to Plugins > Add New > Upload to update to version 3.8.6 or later
  6. 6. Alternatively, download the latest version of IdealAuto from a trusted source and upload via Plugins > Add New > Upload
  7. 7. After installation, verify the plugin version shows 3.8.6 or higher
  8. 8. Test critical functionality to ensure the update did not break site operations

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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