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

CVE-2025-22508

HIGH · 8.1 CVSS v3.1 Published 2025-01-09
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 roninwp FAT Event Lite fat-event-lite allows PHP Local File Inclusion.This issue affects FAT Event Lite: from n/a through <= 1.1.

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 Local File Inclusion (LFI) vulnerability in the roninwp FAT Event Lite WordPress plugin. The vulnerability exists due to improper control of filenames in PHP include/require statements, allowing attackers to manipulate file paths and potentially read sensitive local files or execute arbitrary PHP code.

MitigationUpdate to a patched version of FAT Event Lite if available. If no update exists, remove the plugin. Otherwise, implement strict input validation on all file path parameters and use allowlists for permitted includes.

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 FAT Event Lite plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'fat-event-lite' or search for 'roninwp' in the plugins list via wp-admin or WP-CLI: wp plugin list --search=roninwp
    Affected if The plugin folder 'fat-event-lite' exists in the WordPress plugins directory or appears in the plugin list
  2. Check the installed plugin version
    View the main plugin PHP file (usually fat-event-lite/fat-event-lite.php) and look for the 'Version' header in the plugin comments, or use WP-CLI: wp plugin get fat-event-lite --format=json
    Affected if The version number cannot be verified against a patched release, or the version matches known vulnerable releases (version comparison needed)
  3. Identify vulnerable PHP include/require paths
    Examine PHP files in the plugin directory for include/require statements that use unsanitized input from $_GET, $_POST, or $_REQUEST parameters in file paths (e.g., include($_GET['file']) or require($path . $_REQUEST['template'])
    Affected if Any PHP file in the plugin contains include/require statements using user-controlled input without proper validation or sanitization routines
  4. Check for path traversal patterns in access logs
    Search web server access logs (Apache/nginx) for requests to the plugin's PHP files containing ../ sequences or /etc/passwd, /wp-config.php, or similar sensitive paths in query parameters
    Affected if Log entries show path traversal attempts (e.g., ?file=../../wp-config.php) targeting the plugin's file inclusion functionality
  5. Verify if the vulnerable feature is accessible
    Test if the plugin's file inclusion functionality is reachable by examining the plugin's routing or direct PHP access points, and check if any authentication is required to trigger the include/require
    Affected if The file inclusion code can be reached without authentication or with low-privileged user access

A user is affected if the roninwp FAT Event Lite plugin is installed and its PHP code contains include/require statements using unsanitized user input, or if exploitation attempts appear in server logs.

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

Update to a patched version of FAT Event Lite if available. If no update exists, remove the plugin. Otherwise, implement strict input validation on all file path parameters and use allowlists for permitted includes.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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