Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as subscriber-level user
-
DeliverySend crafted update_license AJAX request
-
ExploitStore unsanitized script payload
-
ExecutionAdministrator opens Activation settings page
-
ImpactScript executes in admin browser context
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 authenticated WordPress account at subscriber level or above on the target site (PR:L), and the ability to invoke the plugin's update_license AJAX action. The stored payload only fires when an administrator subsequently navigates to the DiviGear > Activation settings page, where the value is echoed unescaped into a single-quoted HTML value attribute - so exploitation is gated on that specific admin action occurring. Limiting factors: no unauthenticated access, affected only on DiviGear Carousel versions ≤5.2.0, and impact is confined to whoever views the Activation page (realistically an administrator). |
| Impact | This is a moderate-risk authenticated Stored XSS (CWE-79) in the niche DiviGear Carousel WordPress plugin. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N, base 6.4) confirms network vector, low complexity, and - critically - PR:L, meaning exploitation requires an authenticated account at subscriber level or above, so this is NOT unauthenticated. The scope change (S:C) reflects that the injected script executes in the administrator's browser context, enabling privilege escalation beyond the low-privileged attacker's own account. No EPSS score, CISA KEV listing, or POC indicator was supplied in the input; per the data, there is no public exploit identified at time of analysis and no evidence of active exploitation. The realistic risk is therefore meaningfully lower than the 'network, low-complexity' metrics alone suggest: the attack needs a pre-existing low-privilege account on the target site AND an administrator to subsequently visit the DiviGear > Activation page. Treat as a genuine but non-emergency patch priority, weighted down by the plugin's limited deployment footprint and the authentication prerequisite. Note: the only references provided are the vendor homepage and the Wordfence threat-intel entry - affected-version and fix data were not independently cross-verified from a vendor changelog. |
| Exploit ScenarioDerived | A low-privileged user (subscriber or above) on a WordPress site running DiviGear Carousel ≤5.2.0 sends a crafted update_license AJAX request containing a malicious script payload, which is stored without sanitization. When an administrator later opens the DiviGear > Activation settings page, the unescaped value is echoed into a single-quoted HTML attribute and the script executes in the admin's authenticated session, enabling session/account takeover actions. No public exploit code was identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 20, 2026
Stored cross-site scripting in the DiviGear Carousel WordPress plugin (all versions through 5.2.0) lets any authenticated user at subscriber level or above write arbitrary script into the site's stored license settings through the plugin's update_license AJAX action. The payload is persisted without sanitization and is echoed unescaped into a single-quoted HTML value attribute on the DiviGear > Activation settings page, so it executes in the browser of an administrator who later opens that page, enabling session theft or privileged actions performed as the victim. Exploitation is gated on a valid low-privilege account and on an administrator visiting the Activation screen; no public exploit code was identified at time of analysis and the issue is not in CISA KEV.
RemediationAI
No vendor-released patch was identified at time of analysis, so the immediate priority is containment: deactivate and remove DiviGear Carousel until DiviGear publishes a fixed build, then monitor https://www.divigear.com/ and the Wordfence advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/f482cda1-fe38-455a-b913-bebb21b7bda4?source=cve) for a patched version above 5.2.0 - the trade-off being loss of carousel functionality on affected pages. If the plugin must stay live, close the injection precondition by disabling or tightly gating self-registration and auditing existing subscriber accounts (side effect: reduced community sign-ups), revoke subscriber capabilities that are not operationally required, and restrict access to the wp-admin DiviGear > Activation page to a named set of administrators so the payload has fewer opportunities to render. Because the payload is already persisted, audit the plugin's license option rows in wp_options for unexpected single quotes, angle brackets, or event-handler attributes and strip any injected values after taking a database backup, and add a WAF rule that blocks requests to admin-ajax.php where the action parameter is update_license and the body contains script-like characters, accepting that this may generate false positives against legitimate license-entry traffic. Notifying administrators to review account sessions and rotate credentials after any suspected visit to the Activation page is also recommended.
Affected VersionsENISA
Affected Packages
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 flaw is a classic CWE-79 stored cross-site scripting chain in a WordPress plugin: the update_license AJAX handler takes attacker-controlled request data and writes it into the plugin's license/activation option without sanitizing it on input, and the DiviGear > Activation settings template then renders that value directly into a single-quoted HTML value attribute without esc_attr()-style output escaping. Because the injection context is a quoted attribute, a payload must first break out of the attribute (for example by supplying an encoded single quote) before injecting an event handler or script-bearing markup - which distinguishes it from raw HTML-body XSS and explains why the CVSS scoring shows limited confidentiality and integrity impact (C:L/I:L) despite a scope change (S:C), since the script runs in the administrator's session against the WordPress admin origin. The AV:N/AC:L/PR:L/UI:N portion of the vector confirms the issue is remotely reachable, requires only low-privileged authenticated access, and needs no victim interaction beyond the administrator's own page visit; subscribers are typically the lowest self-registrable role on WordPress sites with open registration, which widens the practical attacker pool. CPE enumeration is not provided in the source data, so version scoping relies on the vendor advisory range of all releases up to and including 5.2.0.
Know when WordPress 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
AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Subscriber account needed so PR:L; stored injection fires in admin context giving S:C with limited C:L/I:L and no availability impact; low complexity and no attacker-side UI.
Primary rating from Vendor (wordfence).
CVSS VectorVendor: wordfence
DescriptionCVE.org
The DiviGear Carousel plugin for WordPress is vulnerable to Stored Cross-Site Scripting via update_license AJAX Action in all versions up to, and including, 5.2.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The injected payload executes when an administrator visits the DiviGear > Activation settings page, where the unsanitized stored value is echoed unescaped into a single-quoted HTML value attribute.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
The mailSend function in the isMail transport in PHPMailer before 5.2.18 might allow remote attackers to pass extra para
The isMail transport in PHPMailer before 5.2.20 might allow remote attackers to pass extra parameters to the mail comman
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
Remote code execution in WordPress 6.9.x (before 6.9.5) and 7.0.x (before 7.0.2) arises from a REST API batch endpoint r
EUVD-2026-104811
GHSA-q774-j486-p33p
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB