If-So Dynamic Content: Editor stored XSS through conversion names
The If-So Dynamic Content WordPress plugin before 1.10.2 does not sanitize a conversion name before storing it, nor escape it when rendering the analytics page, allowing users with editor-level access to store JavaScript that executes in the session of a higher-privileged user who views that page. The authoritative export does not name the request parameter or handler beyond the affected feature described above. The authoritative export identifies the fixed release as 1.10.2.
- Component
- If-So Dynamic Content
- Plugin slug
if-so- Affected
- 1.9.9 to < 1.10.2
- Safe version
1.10.2- Published
- Oct 01, 2026
- Weakness
- Not assigned
This CVE was published Oct 01, 2026 and is one of 10 known issues for this plugin.
Update, patch or deactivate.
Update If-So Dynamic Content to 1.10.2 or a later supported release. An application-level fix should validate stored/request input and escape it for the final HTML, attribute, URL or DOM context. Remove persisted malicious content where storage is involved.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The If-So Dynamic Content WordPress plugin before 1.10.2 does not sanitize a conversion name before storing it, nor escape it when rendering the analytics page, allowing users with editor-level access to store JavaScript that executes in the session of a higher-privileged user who views that page.