Skip to main content

If-So Dynamic Content CVE-2026-100507

| EUVDEUVD-2026-89937 HIGH
Cross-site Scripting (XSS) (CWE-79)
2026-09-30 Patchstack GHSA-gw84-6h89-7r4f
7.1
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Craft malicious link with XSS payload
  2. Delivery
    Lure victim to click/visit
  3. Exploit
    Unsanitized input reflected into page
  4. Execution
    Script executes in victim browser
  5. Impact
    Hijack session or perform actions as victim

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires an active WordPress installation running the If-So Dynamic Content Personalization plugin at version 1.10.1 or earlier. Exploitation is unauthenticated (PR:N) and remote (AV:N) but MANDATORILY requires victim user interaction (UI:R) - the target must click a crafted link or load an attacker-influenced page for the payload to reflect and execute; there is no server-side compromise without that interaction. The specific vulnerable parameter/endpoint is not disclosed in the available data, so precise triggering input cannot be named. Impact is confined to script execution in the victim's browser session (C:L/I:L/A:L), not direct server code execution.

Impact

This is a moderate-severity, unauthenticated reflected/DOM XSS in the If-So Dynamic Content Personalization WordPress plugin (<=1.10.1), rated CVSS 3.1 7.1 (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L). The network vector, low complexity, and no-privileges requirement make it broadly reachable, but exploitation is gated by user interaction (UI:R) - a victim must be lured into clicking a crafted link or visiting an attacker-controlled page, which meaningfully lowers real-world exploitation likelihood versus a fully wormable flaw. The scope-change (S:C) reflects script executing in the victim's browser context against the WordPress origin, hence the low-but-present C/I/A impacts. Signals are consistent but thin: there is NO EPSS score, NO CISA KEV listing, and NO public POC provided in the input, so exploitation status is 'no public exploit identified at time of analysis.' There is no conflict between the CVSS vector and the description (both indicate unauthenticated network XSS requiring interaction). Net: a genuine issue worth patching promptly on affected sites, but not an emergency - treat as routine-to-elevated remediation rather than active-threat priority, driven mainly by the plugin's WordPress footprint rather than any exploitation evidence.

Exploit ScenarioDerived

An attacker crafts a URL or web page containing a malicious payload targeting the vulnerable If-So parameter and lures a site visitor or administrator into clicking it. When the page renders, unsanitized input is reflected into the DOM and the attacker's JavaScript executes in the victim's browser under the WordPress site's origin, enabling session/cookie theft or actions on behalf of the victim. No public exploit code was identified in the provided data, and successful exploitation depends on the victim performing the required interaction.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 30, 2026

Reflected cross-site scripting in the If-So Dynamic Content Personalization plugin for WordPress (versions up to and including 1.10.1) lets unauthenticated remote attackers inject and execute arbitrary JavaScript in a victim's browser session. Exploitation is conditional on victim interaction - an administrator or site visitor must click a crafted link or load an attacker-influenced page - so there is no server-side compromise without that step; the assessed CVSS 3.1 score is 7.1 (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L). There is no CISA KEV listing and no public exploit identified at time of analysis, so this is a moderate-severity, broadly applicable WordPress plugin risk rather than a confirmed active campaign.

RemediationAI

No vendor-released patch identified at time of analysis - the provided data gives no fixed version number, so the first action is to check the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/if-so/vulnerability/wordpress-if-so-dynamic-content-personalization-plugin-1-10-1-cross-site-scripting-xss-vulnerability?_s_id=cve and the WordPress plugin repository for a release newer than 1.10.1 and upgrade to it as soon as it is published. If no fixed release is available yet, the most reliable compensating control is to deactivate the If-So Dynamic Content Personalization plugin entirely until a patched build ships; the trade-off is loss of conditional/personalized content functionality, so sites that depend on it should instead restrict where it is rendered (avoid shortcode/parameter output on publicly reachable templates) and keep it out of unauthenticated visitor paths where possible. Because exploitation mandates victim interaction (UI:R), reinforcing a Content Security Policy that disallows inline and untrusted script sources on site pages substantially blunts the payload - note that aggressive script-src policies can break legitimate inline scripts from other plugins and must be rolled out in report-only mode first. A WAF or reverse-proxy rule that filters script and event-handler patterns from query strings and POST bodies reaching the plugin's endpoints adds defense for older versions, but it is signature-based and can be bypassed with encoding tricks, so treat it as temporary. Finally, because the payload is delivered via a crafted link, instruct site administrators and editors not to open unsolicited links while logged in, and remember that server-side hardening alone will not fix this class of client-side issue - removal or upgrading the plugin is the only complete fix.

Affected VersionsENISA

If-So Dynamic Content Personalization n/a ≤1.10.1

Affected Packages

euvd if_so_dynamic_content_personalization no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability is CWE-79 (Improper Neutralization of Input During Web Page Generation / cross-site scripting) in the WordPress plugin If-So Dynamic Content Personalization, a conditional-content plugin used to show or hide page elements based on visitor conditions, referrers, dates, and similar rules. The CPE record cpe:2.3:a:if-so_dynamic_content:if-so_dynamic_content_personalization:*:*:*:*:*:*:*:* identifies a single vendor/product namespace with an unbounded wildcard version, meaning the CPE itself does not cap the affected range; the version ceiling of 1.10.1 comes from the advisory text. Root cause is the plugin echoing attacker-supplied input into a generated HTML response without output encoding or contextual escaping, allowing script markup to break out of its intended context and execute in the origin of the affected WordPress site. The CVSS vector confirms this is network-reachable and unauthenticated (AV:N/PR:N) with low attack complexity once a lure is delivered, but UI:R makes the victim's click/load mandatory, and S:C reflects that the injected script runs in the scope of the WordPress site's origin. Impact is limited to browser-side confidentiality, integrity, and availability of the victim session (C:L/I:L/A:L) - session/cookie theft, content manipulation, or redirection - not direct remote code execution on the server. The exact vulnerable parameter or endpoint is not disclosed in the available data, so the precise triggering request cannot be named.

Know when Wordpress Plugin gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Patchstack) PRIMARY 7.1 HIGH
AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
vuln.today AI 7.1 HIGH

Unauthenticated network-reachable XSS (PR:N/AV:N/AC:L) requiring victim click (UI:R), executing in the site origin (S:C) with limited browser-context impact (C/I/A:L).

3.1 AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

DescriptionCVE.org

Unauthenticated Cross Site Scripting (XSS) in If-So Dynamic Content Personalization <= 1.10.1 versions.

Executive ViewAI

Why It Matters

The If-So Dynamic Content Personalization plugin for WordPress (versions up to and including 1.10.1) contains a reflected cross-site scripting flaw that can let unauthenticated attackers execute arbitrary JavaScript in an administrator's or visitor's browser session when they interact with a crafted link. Because no vendor patch is available and the plugin is broadly applicable to public-facing WordPress sites, this creates material risk of browser-session compromise and potential unauthorized actions within the site, which could affect users and damage trust. Leadership should prioritize identifying and mitigating exposed installations while monitoring for signs of attempted exploitation.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: remove or disable the If-So Dynamic Content Personalization plugin (versions up to and including 1.10.1) where it is not business-critical; apply WAF or virtual patching rules to block reflected XSS payloads; enforce a restrictive Content Security Policy; restrict wp-admin access and require MFA; train administrators and visitors not to click unsolicited links; and monitor web logs for exploitation attempts. Apply vendor patch when released.

Threat Intelligence Overview

EPSS Score
0.3%
Top 85% exploitable
Prevalence
Medium
third-party WordPress personalization plugin, moderate install base
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Partial

Priority Score

36
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

CVE-2023-6553 CRITICAL POC
9.8 Dec 15

The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1

CVE-2024-5084 CRITICAL POC
9.8 May 23

The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil

CVE-2024-44000 CRITICAL POC
9.8 Oct 20

Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote

CVE-2020-36847 CRITICAL POC
9.8 Jul 12

The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner

CVE-2025-27007 CRITICAL POC
9.8 May 01

The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut

CVE-2016-1209 CRITICAL POC
9.8 May 14

The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via

CVE-2024-4443 CRITICAL POC
9.8 May 22

The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based

CVE-2024-1698 CRITICAL POC
9.8 Feb 27

SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a

CVE-2023-6875 CRITICAL POC
9.8 Jan 11

The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i

CVE-2024-1512 CRITICAL POC
9.8 Feb 17

The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base

CVE-2024-4295 CRITICAL POC
9.8 Jun 05

The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in

CVE-2024-50498 CRITICAL POC
10.0 Oct 28

Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy