CVE-2026-8898
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 Events In City plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'org-events' shortcode in versions up to, and including, 3.0. This is due to insufficient input sanitization and output escaping on user supplied attributes (such as 'organizer_id', 'width', 'height', 'transparency', 'header', 'border', and 'layout') in the org_event_scode() function. The attribute values are concatenated directly into HTML attributes without esc_attr(). 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 Events In City WordPress plugin has a stored XSS vulnerability in the org_event_scode() function. The shortcode handler for 'org-events' accepts user-supplied attributes (organizer_id, width, height, transparency, header, border, layout) and concatenates them directly into HTML output without esc_attr() escaping, allowing authenticated contributors+ to inject malicious scripts.
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.
-
Identify if Events In City plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Events In City' or check wp-content/plugins directory for events-in-city folder. Use wp plugin list or inspect filesystem.Affected if Plugin is present in the WordPress installation
-
Determine the installed plugin versionIn WordPress admin Plugins page, click on the plugin name to view details and note the version number. Alternatively, read the main plugin PHP file header for 'Version:' tag.Affected if Version cannot be determined or is prior to any patched release
-
Check for shortcode usage in contentSearch WordPress database: SELECT * FROM wp_posts WHERE post_content LIKE '%[org-events%' AND post_status IN ('publish','draft','pending'). Also check for the shortcode in page builders or theme files.Affected if The [org-events] shortcode appears in any published content
-
Review user roles with contributor-level accessGo to Users > All Users in WordPress admin and identify any accounts with 'Contributor', 'Author', 'Editor', or 'Administrator' roles. These roles can create content with shortcodes.Affected if Any user account with contributor or higher privilege exists on the site
If the Events In City plugin is installed and the [org-events] shortcode is in use, any authenticated user with contributor access or higher could inject malicious scripts through unsanitized shortcode attributes.
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 dataApply output escaping (esc_attr()) to all user-supplied attributes before rendering them in HTML, and add input validation/sanitization in the org_event_scode() function. Update to any patched version if available.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8898 — 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-8898 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