← All security briefings

Attention

Thim Kit for Elementor: stored script injection through post comments, fixed in 1.4.9

Identifiers: CVE-2026-122230

Published
Last substantive change
Last verified

Last verified: . Attention items are due for re-verification within 72 hours.

Summary

Wordfence Intelligence published CVE-2026-122230 on November 20, 2026, credited to UKO. It affects the WordPress plugin Thim Kit for Elementor (slug thim-elementor-kit) in versions 1.4.8 and earlier; Patchstack lists the same range and cites Wordfence as its source. The plugin's WordPress.org release readme shows version 1.4.9 available since November 4, 2026, so the fix predates the public disclosure. The issue is in this plugin, not in Elementor itself.

Classification reason: Attention. A vendor fix (1.4.9) is available, Wordfence and Patchstack report the same affected range, and exposure depends on a specific template configuration that an administrator can check.

Impact

Script placed in a post comment can be stored and then run in the browser of a visitor who opens the affected post. According to Wordfence, the affected path does not require the attacker to hold an account on the site. What happens in the visitor's browser depends on the injected script; redirects or altered page content are typical examples of this class of issue.

Who is affected

Applies when the plugin is at 1.4.8 or earlier and a Single Post template uses the plugin's Post Comment widget with the Text Reveal entrance animation in the initial viewport, with attacker-supplied comments visible to visitors. Exposure includes comments that moderation lets through, or sites where moderation is off. A normal page visit can render the unsafe content.

Products and versions

Products and versionsAffectedFixed
Thim Kit for Elementor <=1.4.8 1.4.9

Exploitation evidence

Exploitation not established. The reviewed sources (Wordfence, Patchstack, and the vendor readme) do not establish exploitation in the wild and do not show that any particular site is compromised. The readme does not name the CVE.

Sources: Wordfence Intelligence, Patchstack

Actions

  1. Confirm the exact plugin and version in the WordPress admin inventory and identify Single Post templates that use the Post Comment widget with Text Reveal.
  2. Arrange a backed-up update to 1.4.9 or a newer patched version, then check that legitimate commenting still works and review the affected templates.
  3. If the update cannot happen immediately, have the maintainer switch off Text Reveal on the affected widgets or temporarily replace the widget.
  4. Keep comment moderation on as a supporting control, not a complete fix. Do not run any test payloads.

Unknowns

  • Whether your site uses the Post Comment widget with Text Reveal on a Single Post template.
  • Whether any comment already abused this on your site before the update.
  • How effective your current moderation settings are in practice.

Sources

  • Wordfence Intelligence · retrieved https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-plugins/thim-elementor-kit/thim-kit-for-elementor-148-unauthenticated-stored-dom-based-cross-site-scripting-via-comment-content
  • Patchstack · retrieved https://patchstack.com/database/wordpress/plugin/thim-elementor-kit/vulnerability/wordpress-thim-kit-for-elementor-pre-built-templates-widgets-for-elementor-plugin-1-4-8-unauthenticated-stored-dom-based-cross-site-scripting-vulnerability
  • ThimPress on WordPress.org · retrieved https://plugins.svn.wordpress.org/thim-elementor-kit/tags/1.4.9/readme.txt

Change history

  1. — Published: November 21, 2026: Published in English and Vietnamese, based on the Wordfence Intelligence disclosure of November 20, 2026, the Patchstack entry that cites Wordfence, and the vendor's WordPress.org readme listing 1.4.9 on November 4, 2026.

Subscribe: RSS feed · JSON Feed · Feed format and fields