ICS Calendar <= 12.0.9 - Reflected Cross-Site Scripting via 'htmltagtitle' Parameter
The ICS Calendar plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'htmltagtitle' parameter in all versions up to, and including, 12.0.9 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. The vulnerability is reachable via the unauthenticated wp_ajax_nopriv_r34ics_ajax AJAX action, which accepts attacker-controlled js_args values merged over stored shortcode configuration without nonce verification, allowing the htmltagtitle key to bypass the normal shortcode allowlist check.
Quick answer
ICS Calendar should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- *-12.0.9
Fixed versions
- 12.0.9.2
How to fix it
ICS Calendar is affected by CVE-2026-9838, a cross-site scripting issue in versions up to 12.0.9. Wordfence lists the official remediation as updating to version 12.0.9.2, or a newer patched version. Prioritize internet-facing WordPress sites, sites with public registration, customer portals, Elementor/page-builder surfaces, and admin workflows where the vulnerable feature is enabled. If immediate patching is not possible, disable the affected plugin or feature, restrict access, and monitor for exploitation until the update is installed.
- Inventory every WordPress site that has ICS Calendar installed, including production, staging, multisite, client, and WooCommerce environments.
- Confirm the installed ICS Calendar version and compare it with the affected range from the Wordfence advisory.
- Update ICS Calendar to version 12.0.9.2, or to a newer vendor-supported patched version from the official WordPress update channel.
- If the update cannot be applied immediately, disable ICS Calendar or the affected feature and restrict access with roles, authentication, WAF rules, or temporary route blocking.
- Review user-generated content, forms, widgets, saved plugin settings, comments, profiles, templates, and page-builder output for injected scripts or unexpected HTML.
- Rotate administrator sessions, API keys, webhook secrets, payment or integration tokens, and affected credentials if logs or content review suggest compromise.
- Clear WordPress, object, CDN, page-builder, security plugin, and browser caches after patching so vulnerable assets or stored payloads are not served.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm the running ICS Calendar version is version 12.0.9.2 or newer, and record the patched version in the remediation ticket.
- Verify the affected fields, widgets, forms, profile data, or settings now sanitize input and escape output instead of rendering executable scripts.
- Review web server, WordPress, security plugin, WAF, database, and application logs for exploitation attempts before and after the fix.
- Retest normal visitor, subscriber, customer, editor, administrator, checkout, form, API, booking, or integration workflows to confirm expected behavior still works.
- Run a fresh Fixnx scan and document the public exposure state, patched version, log review, and any cleanup evidence.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-9838?
ICS Calendar versions listed as affected should be reviewed: *-12.0.9.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.