dbcve.org
EventinWordPress extension · Themewinter

CVE-2025-39584

HIGH · 7.5 CVSS v3.1 Published 2025-04-16
Fix available
A fix is available. Upgrade to 4.0.26 or later.
See remediation →
81/100
Remediation priority · High
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.25.

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 confidence

A PHP Local File Inclusion vulnerability exists in the Eventin (wp-event-solution) WordPress plugin through version 4.0.25. The plugin improperly controls filenames used in include/require statements, allowing attackers to include arbitrary local PHP files via crafted requests. This can lead to sensitive file disclosure and potentially remote code execution.

MitigationUpdate Eventin plugin to the latest patched version. If no update is available, disable the plugin until a patch is released. Alternatively, implement input validation/sanitization on file inclusion logic to prevent path traversal.

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.26

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 checks

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

  1. Verify Eventin plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Eventin' or 'wp-event-solution' in the list. Alternatively, check the /wp-content/plugins/ directory for an 'eventin' folder.
    Affected if The Eventin plugin folder exists in the WordPress installation.
  2. Check installed version number
    In WordPress admin, find the Eventin plugin in Plugins > Installed Plugins and look at the version number displayed below the plugin name. Alternatively, open /wp-content/plugins/eventin/readme.txt and check the version in the header.
    Affected if The installed version is lower than 4.0.26.
  3. Confirm plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify the Eventin plugin shows 'Active' status. The vulnerability requires the plugin to be active to be exploitable.
    Affected if The Eventin plugin is activated on the site.

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

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.26 or later
Fixed in 4.0.26
Interim mitigation

Update Eventin plugin to the latest patched version. If no update is available, disable the plugin until a patch is released. Alternatively, implement input validation/sanitization on file inclusion logic to prevent path traversal.

Recommended fix High confidence

4.0.26

  1. 1. Backup your WordPress database and files before any upgrade
  2. 2. Navigate to Plugins > Installed Plugins in WordPress admin dashboard
  3. 3. Find the Eventin plugin (wp-event-solution)
  4. 4. If an update to version 4.0.26 is available, click 'Update Now'
  5. 5. Alternatively, download version 4.0.26 from the official WordPress plugin repository or the vendor
  6. 6. Deactivate the current plugin version, delete it, then install the updated version
  7. 7. Reactivate the plugin and verify the event functionality still works correctly

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

Fix this in Eventin Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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