CVE-2026-2396
Stored XSS in Google Calendar List View Plugin for WordPress
Publication date: 2026-04-15
Last updated on: 2026-04-15
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wordfence | list_view_google_calendar_plugin | to 7.4.3 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The List View Google Calendar plugin for WordPress has a Stored Cross-Site Scripting (XSS) vulnerability in all versions up to and including 7.4.3. This vulnerability arises because the plugin does not properly sanitize input or escape output in the event description field.
Authenticated attackers with administrator-level access can exploit this flaw to inject arbitrary web scripts into pages. These scripts execute whenever a user accesses the affected page.
This vulnerability specifically affects multi-site WordPress installations or installations where the unfiltered_html setting is disabled.
How can this vulnerability impact me? :
This vulnerability can allow an attacker with administrator privileges to inject malicious scripts into the website. These scripts can execute in the context of users visiting the infected pages.
Potential impacts include theft of user credentials, session hijacking, defacement of the website, or performing actions on behalf of other users without their consent.
Because the vulnerability requires administrator-level access and affects multi-site or restricted HTML installations, the risk is somewhat limited but still significant in those environments.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, ensure that your List View Google Calendar plugin for WordPress is updated to a version later than 7.4.3.
Additionally, since the vulnerability affects only multi-site installations and installations where unfiltered_html is disabled, review your WordPress configuration to verify these settings.
Limit administrator-level access to trusted users only, as the vulnerability requires authenticated administrator privileges to exploit.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability affects the List View Google Calendar plugin for WordPress versions up to and including 7.4.3, specifically in multi-site installations or where unfiltered_html is disabled. Detection involves verifying the plugin version and configuration.
- Check the installed version of the List View Google Calendar plugin to see if it is version 7.4.3 or earlier.
- Confirm if the WordPress installation is multi-site and if the unfiltered_html capability is disabled.
- Look for suspicious or unexpected scripts in event descriptions within the plugin's stored data.
Example commands to check the plugin version and configuration on the server might include:
- Use WP-CLI to check plugin version: wp plugin list --status=active
- Search the database for suspicious script tags in event descriptions, e.g., using SQL: SELECT * FROM wp_posts WHERE post_content LIKE '%<script>%';
- Check if unfiltered_html is disabled by reviewing user capabilities or site settings.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows authenticated attackers with administrator-level access to inject arbitrary web scripts via stored cross-site scripting in the event description. This can lead to unauthorized access or manipulation of data when users access the injected pages.
Such unauthorized script execution and potential data exposure could negatively impact compliance with data protection standards and regulations like GDPR and HIPAA, which require safeguarding personal and sensitive information against unauthorized access and ensuring data integrity.
However, the vulnerability only affects multi-site installations and installations where unfiltered_html has been disabled, which may limit the scope of impact.