CVE-2025-47494
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 Ashan Perera EventON eventon-lite allows PHP Local File Inclusion.This issue affects EventON: from n/a through <= 2.4.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 confidenceA PHP Local File Inclusion (LFI) vulnerability exists in the EventON eventon-lite plugin (versions through 2.4.1) where user-supplied input is used in include/require statements without proper validation, allowing attackers to read sensitive local files via 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if EventON eventon-lite plugin is installedLocate the plugin files in the WordPress plugins directory (typically wp-content/plugins/eventon-lite/) and check for the main plugin file containing version metadataAffected if The plugin directory exists and contains eventon-lite files
-
Determine the installed plugin versionOpen the main plugin PHP file and locate the version constant or header (e.g., 'Version: x.x.x' in file comments)Affected if The version is 2.4.1 or lower
-
Locate PHP files using include/require with dynamic inputSearch the plugin directory for PHP files containing include, require, include_once, or require_once statements that reference variables (e.g., include($_, include($_GET[], include($REQUEST) without sanitizationAffected if Dynamic file inclusion code using unsanitized user input is found in the plugin files
-
Verify path traversal vulnerability in file inclusionExamine the identified include/require code paths to confirm user-supplied parameters (GET, POST, REQUEST) are used directly in file paths without validation (e.g., no realpath(), basename(), or whitelist checks)Affected if User-controlled parameters flow directly to include/require without validation allowing path traversal (e.g., ../../etc/passwd)
-
Test if vulnerable parameter is accessibleIf a vulnerable parameter is identified, attempt a controlled test request with a benign path traversal (e.g., ?param=../../config) to confirm the parameter is not sanitizedAffected if The parameter accepts path traversal sequences without blocking or sanitizing them
User is affected if they have EventON eventon-lite plugin version 2.4.1 or lower with accessible PHP code that uses user input in include/require statements without validation.
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 to a patched version if available; otherwise, implement strict input validation using a whitelist approach on all file inclusion parameters and disable include/require for user-controlled paths.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47494 — 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-47494 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