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

CVE-2025-58637

HIGH · 7.5 CVSS v3.1 Published 2025-09-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
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
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in immonex immonex Kickstart immonex-kickstart allows PHP Local File Inclusion.This issue affects immonex Kickstart: from n/a through <= 1.11.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

A PHP Local File Inclusion vulnerability in immonex Kickstart allows attackers to include arbitrary local files due to improper validation of file paths in include/require statements. This could enable code execution or exposure of sensitive system files.

MitigationUpdate to a version beyond 1.11.6 which contains the security patch. Additionally, implement strict input validation and whitelist-based file inclusion controls to prevent path traversal.

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

CVSS:3.1/AV:N/AC:H/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. Identify immonex Kickstart installation
    Search for the immonex Kickstart plugin/component in your CMS or PHP application directory. Check plugin metadata files (e.g., readme.txt, plugin header comments) or the main PHP entry file for the plugin name and version declaration.
    Affected if The plugin or component is found and the version cannot be determined or is 1.11.6 or earlier
  2. Determine installed version
    Locate the version number in the main plugin file (typically contains a version constant or variable) or in the plugin's readme/changelog file. Compare your version against the affected range.
    Affected if The installed version is 1.11.6 or lower
  3. Inspect include/require usage
    Search the immonex Kickstart PHP source files for dynamic include/require statements that use variables or user-controlled input without proper sanitization (e.g., include($_GET['file'], include $file, require $path . '.php').
    Affected if Dynamic file inclusion calls are present and accept external input without validation
  4. Check for path traversal exposure
    Review the application's parameter handling to see if any GET/POST parameters are passed directly to include/require functions. Test by attempting to include a known local file (e.g., ../../wp-config.php) with a controlled request if you have a testing environment.
    Affected if URL parameters appear to control file inclusion paths without sanitization or whitelisting
  5. Review server configuration
    Check if PHP allow_url_include is enabled (should be disabled) and verify that the web server user has minimal filesystem permissions. Examine .htaccess or nginx config for restrictions on file access patterns.
    Affected if allow_url_include is On or the application has unnecessary read access to system files

You are affected if immonex Kickstart is installed with version 1.11.6 or lower AND the application exposes dynamic file inclusion logic that accepts unsanitized input.

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

Update to a version beyond 1.11.6 which contains the security patch. Additionally, implement strict input validation and whitelist-based file inclusion controls to prevent path traversal.

Recommended fix Moderate confidence

Latest version after 1.11.6 (check vendor for exact release containing the fix)

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Update immonex Kickstart to the latest available version from the WordPress plugin repository or the vendor's official source
  3. 3. Verify the update was successful by checking the plugin version in WordPress admin > Plugins
  4. 4. Review the plugin's changelog to confirm the security fix is included
  5. 5. Test critical functionality on your site to ensure the update doesn't break existing features
Caveat Minor/None expected - review changelog for any compatibility notes

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
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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