dbcve.org
FotonWordPress extension · Qodeinteractive

CVE-2025-39458

HIGH · 8.1 CVSS v3.1 Published 2025-05-19
Fix available
A fix is available. Upgrade to 2.6.1 or later.
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 Mikado-Themes Foton foton allows PHP Local File Inclusion.This issue affects Foton: from n/a through <= 2.5.2.

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 Mikado-Themes Foton WordPress theme (versions <= 2.5.2) allows remote attackers to include and execute arbitrary files from the server's filesystem via improperly sanitized input parameters in PHP include/require statements.

MitigationUpdate to the latest patched version of the Foton theme. If no patch is available, implement strict input validation on all file inclusion parameters and ensure allow_url_include is disabled in PHP configuration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FotonWordPress extension
Affected:< 2.6.1

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 the installed Foton theme version
    Locate the theme's version information in the theme's style.css file (typically at /wp-content/themes/foton/style.css) or in the theme.json file. The version is listed in the theme header comment as 'Version: x.x.x'. Compare this version number to the affected range: versions < 2.6.1 are vulnerable.
    Affected if The installed Foton theme version is 2.5.2 or lower, or any version below 2.6.1.
  2. Verify the theme is active on the WordPress site
    Check if the Foton theme is currently activated by examining the wp_options table in the WordPress database (option_name = 'template' or 'stylesheet') or through the WordPress admin dashboard under Appearance > Themes.
    Affected if The Foton theme is the active (currently used) theme on the WordPress installation.
  3. Identify exposed file inclusion parameters
    Review PHP source files within the theme directory for include, require, include_once, or require_once statements that accept user-supplied input without proper sanitization. Common vulnerable patterns include: include($_GET['param']), include($_REQUEST['file']), or similar dynamic file inclusion using unsanitized request parameters.
    Affected if The theme contains PHP files with dynamic file inclusion statements that use unsanitized request parameters.
  4. Check PHP configuration for allow_url_include
    Inspect the PHP configuration file (php.ini) or run 'php -i' or 'phpinfo()' to check the value of the allow_url_include directive. This directive controls whether PHP allows including files from URLs.
    Affected if allow_url_include is enabled (set to On) in PHP configuration, which would allow remote file inclusion in addition to local file inclusion.
  5. Review web server logs for suspicious file inclusion requests
    Examine web server access logs (typically in /var/log/apache2/ or /var/log/nginx/) for patterns like '../', '..\', or file paths being passed as query parameters to Foton theme PHP files.
    Affected if Logs show requests with directory traversal sequences or file paths being passed to Foton theme endpoints.

A user is affected if the Foton theme (Qodeinteractive or Mikado-Themes) version is below 2.6.1 and the theme contains vulnerable file inclusion code with exposed parameters.

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
Upgrade available Upgrade to 2.6.1 or later
Fixed in 2.6.1
Interim mitigation

Update to the latest patched version of the Foton theme. If no patch is available, implement strict input validation on all file inclusion parameters and ensure allow_url_include is disabled in PHP configuration.

Recommended fix High confidence

2.6.1

  1. Update the Mikado-Themes Foton theme to version 2.6.1 or later
  2. After upgrading, verify the theme version is correctly installed and the vulnerability is resolved

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

Fix this in Foton Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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