CVE-2025-32614
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.
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 vulnerability in the EventON eventon-lite plugin (versions <= 2.4) allows attackers to include arbitrary local PHP files through unsanitized file inclusion parameters, potentially leading to remote code execution.
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
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Locate EventON plugin installationCheck for the eventon-lite plugin directory in your WordPress installation at wp-content/plugins/eventon-lite/ or wp-content/plugins/eventon/Affected if The plugin directory exists in your WordPress plugins folder
-
Determine installed versionOpen the main plugin PHP file (e.g., eventon-lite.php) and locate the version comment header or version constant near the top of the fileAffected if The version number displayed is 2.4 or lower
-
Identify vulnerable file inclusion codeSearch the plugin source code for file inclusion functions (include, include_once, require, require_once) where user input parameters are used directly without sanitization - look for patterns like include($_GET['param']) or similar dynamic file includesAffected if Such unsafe file inclusion patterns exist in the plugin code with unsanitized user-controlled parameters
-
Verify exposure of inclusion parametersCheck if the identified vulnerable parameter names (e.g., _GET or _POST parameters used in the file inclusion) are accessible via HTTP requests to your WordPress site - test by making a request with a benign path like ?param=../../wp-config.phpAffected if The vulnerable parameter is accepted via URL or POST without authentication checks and the file inclusion executes
You are affected if EventON plugin version 2.4 or lower is installed and the vulnerable file inclusion parameter is accessible and usable without sanitization.
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 of EventON; until available, implement strict input validation on all file inclusion parameters and ensure allow_url_include is disabled in PHP configuration.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32614 — 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-32614 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