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

CVE-2025-49416

HIGH · 8.1 CVSS v3.1 Published 2025-06-27
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 Fastw3b LLC FW Gallery fw-gallery allows PHP Local File Inclusion.This issue affects FW Gallery: from n/a through <= 8.0.0.

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 Local File Inclusion (LFI) vulnerability in Fastw3b FW Gallery plugin allows attackers to manipulate filename parameters in PHP include/require statements to load arbitrary files from the server. This occurs due to improper input validation on file path parameters, potentially enabling code execution if attacker-controlled files can be uploaded or sensitive files read.

MitigationImplement strict input validation using whitelist approaches for allowed files, apply basename() and realpath() sanitization to prevent directory traversal, and consider updating to a patched version if available. Disable allow_url_include if not needed.

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 Fastw3b FW Gallery plugin is installed
    Search the web server file system for the FW Gallery plugin directory, typically found in wp-content/plugins/ or similar plugin paths for the CMS in use. Use a command like 'find /var/www -type d -iname "*fw*gallery*"' or inspect the plugin list via the CMS admin panel if available.
    Affected if The plugin directory exists on the server and the plugin is active in the CMS.
  2. Determine the installed version of FW Gallery
    Locate the main plugin PHP file (often named main.php, index.php, or similar within the plugin directory) and read the file header comments which typically contain the version number. Alternatively, check for a version.php or readme.txt file within the plugin folder.
    Affected if The installed version cannot be confirmed as patched, or no version information is found in the plugin files.
  3. Verify PHP include/require functions are accessible to the plugin
    Review the plugin source code, specifically looking for include(), require(), include_once(), or require_once() statements that process user-supplied filename parameters without sanitization. Search for patterns like 'include($_GET' or 'require($' within the plugin directory.
    Affected if The plugin code contains include/require statements that accept unsanitized input from request parameters.
  4. Check if the web application accepts file path parameters
    Examine HTTP request parameters sent to the plugin endpoints (typically in wp-admin/admin-ajax.php or plugin-specific PHP files). Look for parameters that accept file paths or filenames, and test whether directory traversal sequences like '../' are processed by the application.
    Affected if The application accepts file path parameters and does not reject directory traversal attempts.

You are affected if the Fastw3b FW Gallery plugin is installed, its version is unknown or unpatched, and the plugin processes file path parameters without proper sanitization allowing directory traversal.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation using whitelist approaches for allowed files, apply basename() and realpath() sanitization to prevent directory traversal, and consider updating to a patched version if available. Disable allow_url_include if not needed.

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-49416 — 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-49416 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