CVE-2026-2387
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 Event Organiser plugin for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to, and including, 3.12.9. This is due to the 'eo_events' shortcode accepting attacker-controlled 'no_events' content and rendering it in event list templates without output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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 Event Organiser WordPress plugin fails to escape output from the 'no_events' parameter in its 'eo_events' shortcode. An authenticated Contributor-level attacker can inject malicious JavaScript into the shortcode content, which will execute in the browsers of any user viewing pages containing the injected shortcode.
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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/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.
-
Verify Event Organiser plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Event Organiser' in the listAffected if The plugin is not installed or not active
-
Determine the installed version of Event OrganiserIn the Plugins list, find Event Organiser and note the version number displayed below the plugin name. Compare this to version 3.13.0Affected if The installed version is lower than 3.13.0
-
Identify pages using the eo_events shortcodeIn WordPress admin, go to Pages or Posts and review content for the shortcode [eo_events]Affected if The eo_events shortcode is present in any published content
-
Inspect shortcode parameters for the no_events attributeExamine any [eo_events] shortcode found and check if it includes a no_events parameter, for example [eo_events no_events="..."]Affected if The shortcode includes a no_events parameter with unescaped content
-
Review page content for suspicious script injectionsView pages containing the eo_events shortcode in a browser or inspect the page source HTML to look for unexpected script tags or event handlersAffected if Malicious JavaScript or unexpected HTML is present in the shortcode output
A user is affected if the Event Organiser plugin version is below 3.13.0 and the eo_events shortcode with a no_events parameter exists in published content that could contain injected scripts.
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 Event Organiser plugin to version 3.13.0 or later, which includes proper output escaping for the shortcode parameters. As an interim measure, review pages using the 'eo_events' shortcode for suspicious content.
- Consultation2.0 h
- Implementation3.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 $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2387 — 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-2387 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