CVE-2025-30895
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 Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in magepeopleteam WpEvently mage-eventpress allows PHP Local File Inclusion.This issue affects WpEvently: from n/a through <= 4.2.9.
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 · high confidenceA Path Traversal vulnerability in the WpEvently WordPress plugin (versions up to 4.2.9) allows attackers to manipulate file paths using directory traversal sequences (../) to include arbitrary PHP local files. This Local File Inclusion (LFI) can lead to remote code execution if attacker-controlled files exist on the server.
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.
-
Locate WpEvently plugin installationCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'wpevently', 'wp-evently', or similar variants. Also check via WordPress admin under Plugins > Installed Plugins.Affected if The WpEvently plugin folder exists in the plugins directory.
-
Determine installed WpEvently versionOpen the main plugin PHP file (usually named wpevently.php, index.php, or plugin.php inside the plugin folder) and locate the Version header in the plugin comment block at the top. Alternatively, check the version in WordPress admin plugin list.Affected if The reported version is 4.2.9 or any version lower than 4.2.9.
-
Verify the plugin is activeCheck WordPress admin under Plugins > Installed Plugins to confirm WpEvently status is 'Active'. Alternatively, query the wp_options table for option_name='active_plugins' and check for the plugin slug.Affected if The plugin is currently active on the WordPress site.
-
Identify file inclusion functionalityExamine the WpEvently plugin files for code that uses PHP include, require, include_once, or require_once with variables derived from user input (e.g., $_GET, $_POST, $_REQUEST). Search for patterns like 'include($' or 'require($' combined with traversal indicators like '../' or '..\'.Affected if The plugin contains file inclusion code that accepts user-controlled path parameters without proper sanitization.
A user is affected if WpEvently plugin version 4.2.9 or lower is installed and active, and the vulnerable file inclusion functionality is present and accessible.
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 WpEvently to the latest patched version. If no patch is available, disable the plugin or implement a WAF rule to block path traversal patterns in requests.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30895 — 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-30895 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