dbcve.org
EventinWordPress extension · Themewinter

CVE-2025-26964

HIGH · 8.8 CVSS v3.1 Published 2025-02-25
Fix available
A fix is available. Upgrade to 4.0.21 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 Arraytics Eventin wp-event-solution allows PHP Local File Inclusion.This issue affects Eventin: from n/a through <= 4.0.20.

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

Local File Inclusion (LFI) vulnerability in the Eventin WordPress plugin (wp-event-solution) up to version 4.0.20 allows attackers to include arbitrary local PHP files due to improper control of filename parameters in include/require statements. This can lead to sensitive file disclosure and potentially remote code execution.

MitigationUpdate Eventin plugin to the latest version when available. If no patch exists, disable the plugin, implement WAF rules to block directory traversal patterns (../), and restrict file inclusion permissions on the server.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
EventinWordPress extension
Affected:< 4.0.21

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Eventin plugin installation
    Check if the Eventin plugin (wp-event-solution) is installed on the WordPress site. Run: ls wp-content/plugins/ or use WordPress admin dashboard under Plugins > Installed Plugins. Look for 'Eventin' or 'wp-event-solution'.
    Affected if The plugin is installed and the version is below 4.0.21
  2. Determine installed Eventin version
    Locate the plugin version number. In the WordPress admin, go to Plugins > Installed Plugins and click on Eventin to view the version in the plugin header. Alternatively, check the main plugin file header in wp-content/plugins/wp-event-solution/wp-event-solution.php for the 'Version' tag.
    Affected if The displayed version number is less than 4.0.21 (for example: 4.0.20, 4.0.19, etc.)
  3. Confirm plugin is active
    In WordPress admin under Plugins > Installed Plugins, verify whether Eventin shows as 'Active' (green underline or 'Activate' button is absent).
    Affected if The plugin is currently active and version is below 4.0.21
  4. Identify vulnerable include/require usage
    Review PHP files within the wp-event-solution plugin directory for dynamic include/require statements that use user-controlled input without sanitization. Search for patterns like 'include($_GET' or 'require($_POST' in the plugin source code. This requires access to the server filesystem or plugin source files.
    Affected if Dynamic file inclusion code using unsanitized request parameters exists in the plugin files

The environment is affected if the Eventin (wp-event-solution) plugin is installed, active, and running a version lower than 4.0.21.

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.

dbcve · scoped
Upgrade available Upgrade to 4.0.21 or later
Fixed in 4.0.21
Interim mitigation

Update Eventin plugin to the latest version when available. If no patch exists, disable the plugin, implement WAF rules to block directory traversal patterns (../), and restrict file inclusion permissions on the server.

Recommended fix High confidence

4.0.21

  1. 1. Back up your WordPress site (database and files) before performing any updates.
  2. 2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins.
  3. 3. Locate the Eventin plugin in the list.
  4. 4. If an update is available, click 'Update Now' to update to version 4.0.21.
  5. 5. Alternatively, download version 4.0.21 from the official WordPress plugin repository or vendor source.
  6. 6. Deactivate and delete the current version, then upload and install version 4.0.21.
  7. 7. After update, verify the plugin is running version 4.0.21 in the plugins list.
  8. 8. Test critical event functionality to ensure the plugin operates correctly after the update.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Eventin Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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