CVE-2026-3585
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 · uneditedThe The Events Calendar plugin for WordPress is vulnerable to Path Traversal in all versions up to, and including, 6.15.17 via the 'ajax_create_import' function. This makes it possible for authenticated attackers, with Author-level access and above, to read the contents of arbitrary files on the server, which can contain sensitive information.
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 confidenceThe Events Calendar WordPress plugin versions up to 6.15.17 contain a path traversal vulnerability in the ajax_create_import function. Authenticated attackers with Author-level permissions or higher can manipulate file path inputs to access arbitrary files on the server, potentially exposing sensitive configuration or system files.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm The Events Calendar plugin is installedLog in to WordPress admin and navigate to Plugins > Installed Plugins, or inspect the file /wp-content/plugins/the-events-calendar/common/src/Tribe/Plugins.php for the version constantAffected if The plugin is present in the WordPress installation
-
Identify the installed plugin versionCheck the plugin version listed in the WordPress Plugins page, or look for the version number in the plugin's main file header (typically the-events-calendar.php)Affected if The version is 6.15.17 or earlier
-
Verify Author-level or higher users existNavigate to Users > All Users in WordPress admin and review user roles, or query the wp_usermeta table for users with wp_capabilities containing 'author', 'editor', or 'administrator'Affected if Any user account has Author, Editor, or Administrator role
-
Check if ajax_create_import function is accessibleInspect the plugin file containing the ajax_create_import function (typically in the import handling code) to confirm the function exists and is hooked to WordPress AJAX, then verify the function lacks proper path sanitizationAffected if The ajax_create_import function exists and handles file path inputs without validation
You are affected if The Events Calendar plugin version is 6.15.17 or earlier AND your site has at least one user with Author-level permissions or higher who could trigger the ajax_create_import function.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate The Events Calendar plugin to version 6.15.18 or later. If immediate update is not possible, restrict Author-level user capabilities or monitor for suspicious file access patterns.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3585 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-3585 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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