dbcve.org
EventinWordPress extension · Themewinter

CVE-2025-47445

CRITICAL · 9.8 CVSS v3.1 Published 2025-05-14
Fix available
A fix is available. Upgrade to 4.0.27 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Relative Path Traversal vulnerability in Arraytics Eventin wp-event-solution allows Path Traversal.This issue affects Eventin: from n/a through <= 4.0.26.

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

Relative path traversal vulnerability in the Eventin WordPress plugin (versions <= 4.0.26) allows attackers to use '..' sequences in file path requests to access files outside the web root directory, potentially exposing sensitive system files or configuration data.

MitigationUpdate Eventin plugin to the latest version when available; if no patch exists, implement web application firewall rules to block path traversal sequences ('..') and restrict file access to intended directories.

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

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm Eventin plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'Eventin' or 'Eventin - Event Conference' in the plugin list.
    Affected if Eventin plugin appears in the installed plugins list
  2. Check installed Eventin version
    In the Installed Plugins list, locate Eventin and view the version number displayed beneath the plugin name. Compare it to the affected version range: versions below 4.0.27 are vulnerable.
    Affected if The installed version is 4.0.26 or lower (< 4.0.27)
  3. Identify exposed file-related endpoints
    Review the website for any public-facing features that accept file path parameters (e.g., file download, template loading, asset retrieval functions). Check for URL parameters that might accept file paths.
    Affected if The plugin exposes any functionality that accepts file path parameters accessible to unauthenticated or authenticated users
  4. Test for directory traversal vulnerability
    If file-related endpoints exist, attempt a safe test request using directory traversal sequences (e.g., ?file=../../wp-config.php). Monitor whether the application returns files from outside the expected directory.
    Affected if The application returns files from directories outside the intended web root when traversal sequences are used

The environment is affected if Eventin plugin versions 4.0.26 or below are installed AND the plugin exposes file path parameters that accept user input without proper sanitization.

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.27 or later
Fixed in 4.0.27
Interim mitigation

Update Eventin plugin to the latest version when available; if no patch exists, implement web application firewall rules to block path traversal sequences ('..') and restrict file access to intended directories.

Recommended fix High confidence

4.0.27 or latest available version

  1. Create a full backup of the WordPress site including database and files
  2. Log in to the WordPress admin dashboard
  3. Navigate to Plugins > Installed Plugins
  4. Locate the Eventin plugin (wp-event-solution)
  5. If automatic updates are enabled, the plugin should update to 4.0.27 or later; otherwise, click 'Update Now'
  6. Alternatively, manually upload the updated plugin version 4.0.27 or later via Plugins > Add New > Upload Plugin
  7. After update, verify the plugin version shows 4.0.27 or newer in the plugins list
  8. Clear any caching layers if present

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

Fix this in Eventin Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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