CVE-2026-8898 MEDIUM

CVE-2026-8898: Events In City <= 3.0 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode Attributes

Vendor Ruchit47
Product Events In City
Weakness CWE-79 · XSS
Published May 27, 2026
Last update May 27, 2026

CVSS base score

6.4/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality Low
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

What the vulnerability does

01Description

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

Explanation of Vulnerability in Simple Terms

02Summary

Events In City versions 3.0 and earlier contain a cross-site scripting vulnerability that allows authenticated users to inject malicious scripts affecting other users on the site. The vulnerability exists because user input is not properly sanitized before being displayed. An attacker with low-level account access can craft a payload that executes in other users' browsers, potentially stealing session data or performing actions on their behalf.

What an attacker can do

03Attacker Capabilities

Inject malicious JavaScript that runs in other users' browsers and affects the entire site.

Potential impact on your site

04Site Impact

Authenticated users can compromise other users' sessions and data; site-wide XSS exposure.

Conditions required to exploit

05Prerequisites

Attacker must have a low-privilege account on the site; no user interaction required from victims.

Key dates

06Disclosure timeline

May 27, 2026 CVE published
May 27, 2026 Record updated