dbcve.org
Ssv EventsWordPress extension · Moridrin

CVE-2024-49286

CRITICAL · 9.8 CVSS v3.1 Published 2024-10-20
Fix available
A fix is available. Upgrade to after 3.2.7 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
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Jeroen Berkvens SSV Events ssv-events allows PHP Local File Inclusion.This issue affects SSV Events: from n/a through <= 3.2.7.

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

A path traversal vulnerability in the SSV Events WordPress plugin (versions up to 3.2.7) allows remote attackers to perform local file inclusion (LFI) by manipulating path parameters, potentially exposing sensitive server files including configuration files, credentials, and source code.

MitigationUpgrade to a patched version if available; otherwise disable the plugin. If the plugin must remain in use, implement input validation using basename() and realpath() to sanitize file path parameters and restrict file access to allowed 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
Ssv EventsWordPress extension
Affected:<= 3.2.7

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 SSV Events plugin is installed
    Navigate to WordPress admin > Plugins, or use WP-CLI command: wp plugin list --status=active --format=csv | grep -i 'ssv events'
    Affected if The plugin appears in the list of active plugins
  2. Identify the installed version
    Check the plugin version in the plugin list view (wp-admin > Plugins), or inspect the plugin's main PHP file header for 'Version:' comment, or run: wp plugin get ssv-events --format=json
    Affected if The version listed is 3.2.7 or any version lower (e.g., 3.2.6, 3.2.5, etc.)
  3. Locate the vulnerable include statement
    Search plugin source files for include/require statements using path variables (e.g., grep -r 'include.*\$_' or look for file inclusion functions that accept user-supplied parameters). Common patterns: include($_GET['file']), include($_REQUEST['path'])
    Affected if File inclusion code references user-controlled parameters without sanitization (e.g., no basename(), no whitelist validation)
  4. Test for unauthenticated path traversal
    With the vulnerable parameter identified, test using known paths: ../../wp-config.php or ../../../../etc/passwd (if server allows). Use curl or browser to send requests like: ?file=../../wp-config.php
    Affected if The server returns file contents (wp-config.php or system files) instead of an error, indicating path traversal is successful

You are affected if the SSV Events plugin version is 3.2.7 or lower AND the plugin exposes an unauthenticated file inclusion endpoint with user-controlled path parameters that can be manipulated with ../ sequences.

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 a release after 3.2.7
Interim mitigation

Upgrade to a patched version if available; otherwise disable the plugin. If the plugin must remain in use, implement input validation using basename() and realpath() to sanitize file path parameters and restrict file access to allowed directories.

Recommended fix Moderate confidence

Latest version of SSV Events plugin available from wordpress.org or the vendor (version higher than 3.2.7)

  1. Check the WordPress plugin repository or contact the vendor to identify the latest available version of SSV Events plugin
  2. Upgrade the SSV Events plugin to the latest version available that includes the security fix
  3. After upgrading, verify the plugin functions correctly on the site
  4. If available, review the plugin changelog to confirm the path traversal vulnerability is addressed
  5. Ensure WordPress core and all other plugins are also kept up to date

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

Fix this in Ssv Events Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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