Live › vulnerability › CVE-2026-118164
Go to dashboardThe If-So Dynamic Content plugin for WordPress fails to sanitize and escape several repeater fields, so authenticated contributors can store script that runs in pages. An attacker gets script execution in the browser of any visitor, or an admin, who opens an injected page.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 07:31 UTC. All times on this page are UTC.
Sites running the If-So Dynamic Content plugin at version 1.10.2 or earlier are exposed, because contributor-level accounts can store script in plugin fields that is output to visitors. Sites without the plugin, or where only trusted editors can create content, have less exposure. unknown whether a specific default configuration is required.
No product ranges from the sources yet.
wp plugin get if-so --field=version1.10.2, as the description says all versions up to and including 1.10.2 are affectedEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
The If-So Dynamic Content – Elementor & All Page Builders Personalization plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'repeater[*][version_uid] (and many sibling fields: freeze-mode, cookie-input, ip-input, compare, utm-value, page-url-compare, group-name, custom, …)' parameter in all versions up to, and including, 1.10.2 due to insufficient input sanitization and output escaping. 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.
This page as .md · .json · in your agent: get_signal("CVE-2026-118164")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.