Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-1922: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in brianhogg The Events Calendar Shortcode & Block

0
Medium
VulnerabilityCVE-2026-1922cvecve-2026-1922cwe-79
Published: Tue Feb 10 2026 (02/10/2026, 09:26:05 UTC)
Source: CVE Database V5
Vendor/Project: brianhogg
Product: The Events Calendar Shortcode & Block

Description

The The Events Calendar Shortcode & Block plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's `ecs-list-events` shortcode `message` attribute in all versions up to, and including, 3.1.2 due to insufficient input sanitization and output escaping on user supplied attributes. 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.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/26/2026, 15:25:53 UTC

Technical Analysis

CVE-2026-1922 is a stored cross-site scripting vulnerability classified under CWE-79, found in the WordPress plugin 'The Events Calendar Shortcode & Block' by brianhogg. The vulnerability exists in all versions up to and including 3.1.2 due to insufficient sanitization and escaping of user-supplied input in the 'message' attribute of the 'ecs-list-events' shortcode. Authenticated attackers with contributor-level permissions or higher can exploit this flaw by injecting arbitrary JavaScript code into event pages. When other users access these pages, the malicious scripts execute in their browsers, potentially compromising session tokens, redirecting users, or performing actions on behalf of the victim. The vulnerability does not require user interaction beyond visiting the infected page and has a CVSS 3.1 base score of 6.4, reflecting medium severity with network attack vector, low attack complexity, and privileges required. The scope is changed (S:C) because the vulnerability can affect other users beyond the attacker. No patches or official fixes are linked yet, and no known exploits have been observed in the wild. This vulnerability highlights the risks of insufficient input validation in WordPress plugins, especially those that allow user-generated content to be rendered on public pages.

Potential Impact

The impact of CVE-2026-1922 is significant for organizations using the affected plugin on WordPress sites, particularly those that allow contributor-level users to create or edit event content. Exploitation can lead to session hijacking, unauthorized actions performed in the context of other users (including administrators), defacement, or distribution of malware via injected scripts. This can compromise the confidentiality and integrity of user data and site content. While availability is not directly impacted, the reputational damage and potential data breaches can be severe. Since the vulnerability requires authenticated access, the risk is somewhat mitigated by access controls; however, many WordPress sites have multiple contributors or editors, increasing the attack surface. The scope change means that the vulnerability affects other users beyond the attacker, amplifying the potential damage. Organizations with public-facing event calendars or community-driven content are particularly vulnerable to exploitation and subsequent attacks such as phishing or privilege escalation.

Mitigation Recommendations

To mitigate CVE-2026-1922, organizations should immediately restrict contributor-level permissions to trusted users only and audit existing event content for suspicious scripts. Applying the latest plugin updates once available is critical; if no patch is yet released, consider temporarily disabling the 'The Events Calendar Shortcode & Block' plugin or removing the vulnerable shortcode usage from pages. Implementing a Web Application Firewall (WAF) with rules to detect and block XSS payloads targeting the 'message' attribute can provide interim protection. Additionally, site administrators should enforce Content Security Policy (CSP) headers to limit script execution sources and regularly scan the site for injected malicious code. Educating contributors about safe content practices and monitoring logs for unusual activity can help detect exploitation attempts early. Finally, consider using security plugins that sanitize shortcode inputs or employing custom filters to validate and escape user inputs before rendering.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2026-02-04T18:02:34.066Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 698afe6e4b57a58fa1f90105

Added to database: 2/10/2026, 9:46:22 AM

Last enriched: 2/26/2026, 3:25:53 PM

Last updated: 3/27/2026, 2:19:57 PM

Views: 98

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses