dbcve.org
EventinWordPress extension · Themewinter

CVE-2025-1770

HIGH · 8.8 CVSS v3.1 Published 2025-03-20
Fix available
A fix is available. Upgrade to 4.0.25 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
The Event Manager, Events Calendar, Tickets, Registrations – Eventin plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 4.0.24 via the 'style' parameter. This makes it possible for authenticated attackers, with Contributor-level access and above, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.

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

The Eventin WordPress plugin versions up to 4.0.24 contain a Local File Inclusion vulnerability via the 'style' parameter. Authenticated attackers with Contributor-level access or higher can include arbitrary files from the server filesystem, potentially leading to remote code execution if they can upload or control included files.

MitigationUpdate the Eventin plugin to version 4.0.25 or later which contains the security fix. If no patch is available, restrict Contributor-level user permissions or disable the plugin until a fix is released.

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

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 is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'eventin' or check the Plugins admin page for 'Eventin' or 'Themewinter Eventin' in the list of installed plugins.
    Affected if The Eventin plugin folder exists in wp-content/plugins/ or appears in the WordPress plugins list.
  2. Check installed Eventin version
    Open the main Eventin plugin file (usually eventin.php) in wp-content/plugins/eventin/ and look for the 'Version:' header in the plugin comments, or check the plugin's readme.txt file.
    Affected if The version number found is less than 4.0.25 (for example: 4.0.24, 4.0.23, etc.).
  3. Confirm plugin is active
    Check the WordPress database table wp_options for the option_name 'active_plugins', or view the Plugins admin page to see if Eventin is activated.
    Affected if Eventin appears in the list of active plugins.
  4. Identify users with Contributor-level or higher access
    Navigate to WordPress Users admin page and review the role column, or query the wp_usermeta table for users with meta_key 'wp_capabilities' containing 'contributor', 'author', 'editor', or 'administrator'.
    Affected if At least one user account has a role of Contributor, Author, Editor, or Administrator.

If the Eventin plugin is installed with a version below 4.0.25, is active, and has at least one Contributor-level user account present, the environment is affected by this vulnerability.

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.25 or later
Fixed in 4.0.25
Interim mitigation

Update the Eventin plugin to version 4.0.25 or later which contains the security fix. If no patch is available, restrict Contributor-level user permissions or disable the plugin until a fix is released.

Recommended fix High confidence

Eventin version 4.0.25

  1. Back up your WordPress site and database before updating any plugins
  2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. Locate the Eventin plugin in the plugin list
  4. Click 'Update now' on the Eventin plugin if an update is available, or manually update to version 4.0.25
  5. Verify the plugin updated successfully to version 4.0.25
  6. Test event creation and related functionality to ensure the update did not break expected features
  7. Review user role permissions to ensure only trusted users have Contributor-level or higher access

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

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

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 locally
dbcve dependency scanner

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