CVE-2025-23915
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 · uneditedImproper 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 confidenceThe FAT Event Lite WordPress plugin versions up to 1.1 contains a PHP Local File Inclusion (LFI) vulnerability due to improper control of filename parameters in include/require statements. An attacker could potentially exploit this to read sensitive files from the server filesystem by manipulating file path parameters.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify FAT Event Lite plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'fat-event-lite' or similar. Alternatively, log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins to confirm the plugin is listed.Affected if The plugin folder exists in wp-content/plugins/ or appears in the WordPress admin plugin list
-
Identify the installed plugin versionOpen the main plugin file (typically fat-event-lite.php or index.php inside the plugin folder) and look for the version number in the plugin header comment (e.g., 'Version: 1.1'). Alternatively, check the readme.txt file in the plugin directory for the 'Stable tag' entry.Affected if The version is 1.1 or any version lower than the latest patched version, indicating the installation falls within the affected range (up to 1.1)
-
Confirm the plugin is activeIn the WordPress admin dashboard, go to Plugins > Installed Plugins and check if FAT Event Lite is activated. Alternatively, query the WordPress database options table for option_name='active_plugins' and check if the plugin's main file is listed.Affected if The plugin appears as 'Active' in the plugin list or is present in the active_plugins array in the database
-
Locate vulnerable include/require code patternsSearch the plugin directory for PHP files containing include, require, include_once, or require_once statements that use variables in the file path (e.g., include($some_variable); or include($_GET['page']);). Specifically examine files in the 'include/' subdirectory mentioned in the CVE description.Affected if Any include/require statement uses a user-controllable variable (such as $_GET, $_POST, or未经过滤的变量) to construct the file path without proper sanitization
A user is affected if the FAT Event Lite plugin is installed with version 1.1 or lower, is actively running on the WordPress site, and contains the vulnerable include/require patterns that allow LFI exploitation.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate FAT Event Lite to the latest patched version. If no patched version is available, disable the plugin until a fix can be applied. As a temporary measure, review and restrict file access permissions on the web server.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-23915 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-23915 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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