EUVD-2026-82854
GHSA-m455-q9mx-cr49
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain contributor-level account
-
DeliveryCreate post with entity-encoded script in title
-
ExploitPayload bypasses sanitize_text_field on save
-
ExecutionAdmin views page, Select2 decodes title
-
ImpactScript executes in victim browser session
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 account with contributor-level capability or above on a WordPress site running Popup Maker ≤1.24.0 (PR:L). The attacker must create a post whose title contains an HTML entity-encoded XSS payload, which bypasses sanitize_text_field on save; the script only fires when the title is later rendered and decoded by the plugin's Select2 admin component and viewed by another user (effectively requiring a victim, typically an admin, to load the affected page). Limiting factors: exploitation depends on the site granting contributor or higher accounts (self-registration or invitation), and impact is confined to browser-side script execution (C:L/I:L) rather than direct server compromise. Patched in version 1.25.0. |
| Impact | This is a moderate-severity stored XSS (CVSS 6.4, CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N) reported by Wordfence. The network vector and low complexity are real, but exploitation is gated behind PR:L - the CVSS vector contains PR:L, meaning an authenticated attacker with contributor-level access or above is required, so this is not an unauthenticated internet-wide risk. The S:C (scope change) and C:L/I:L reflect that injected script executes in the browser of any user who views the page, including higher-privileged admins, enabling limited confidentiality/integrity impact (session/DOM access) rather than direct server compromise. No EPSS score, no CISA KEV listing, and no public POC are provided in the input, so there is no signal of active exploitation or automation; the risk is a targeted privilege-escalation-via-XSS scenario, not mass exploitation. Net: a genuine but lower-priority issue whose real-world severity depends on how freely a given site grants contributor accounts. The specific bypass mechanism (HTML entity-encoded title surviving sanitize_text_field, then decoded by the Select2 admin component) is well-documented by Wordfence, lending high confidence to the technical description. |
| Exploit ScenarioDerived | An attacker who holds (or registers for) a contributor-level account on a WordPress site running Popup Maker ≤1.24.0 creates a post whose title contains an HTML entity-encoded script payload; the payload survives sanitize_text_field on save. When an administrator or other user later views the affected admin/page area, the Select2 component decodes and renders the title, executing the attacker's JavaScript in the victim's authenticated browser session. No public POC or active exploitation is reported in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 18, 2026
Stored cross-site scripting in the Popup Maker plugin for WordPress versions up to and including 1.24.0 allows authenticated attackers with contributor-level access or higher to inject persistent JavaScript into post titles, which executes in the browsers of users viewing affected admin pages. The vulnerability has a CVSS score of 6.4 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N) and is reported by Wordfence; no public exploit code or active exploitation has been identified at time of analysis. The issue is patched in version 1.25.0.
RemediationAI
Update the Popup Maker plugin to version 1.25.0 immediately. The changeset at https://plugins.trac.wordpress.org/changeset/3690634/popup-maker/trunk/classes/Admin/Ajax.php and the tag diff from 1.24.0 to 1.25.0 show the fix applied to the vulnerable code. If an immediate update is not feasible, restrict contributor-level and higher accounts to fully trusted users only, as the vulnerability requires such an account to inject the malicious title; however, this is a mitigation rather than a complete fix. There is no known configuration toggle to disable the vulnerable Select2 rendering without updating the plugin. Refer to the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/973b23c6-4edd-4f89-b5cf-68e83cfdb8ac?source=cve for additional details and monitoring guidance.
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
This is a stored cross-site scripting (XSS) vulnerability classified as CWE-79, arising from insufficient input sanitization and output escaping of the post_title field within the Popup Maker WordPress plugin. The root cause involves a bypass of the WordPress sanitize_text_field function: an attacker can save a post title containing an HTML entity-encoded payload, which is not neutralized on save. When the title is later rendered by the plugin's Select2 component-a JavaScript library used to enhance select boxes in the admin interface-the browser decodes the entity and executes the script. The vulnerable code paths are located in classes/Admin/Ajax.php (lines around 152 and 163), classes/Helpers.php (line 192), and the distributed JavaScript file dist/assets/admin-general.js. The CVSS vector indicates network attack, low complexity, low privileges required, no user interaction for the attack itself, scope change, and limited confidentiality and integrity impact.
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
AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Contributor-level auth required (PR:L); stored payload executes without further attacker interaction (UI:N); cross-context execution in victim browser yields S:C with limited C:L/I:L and no availability impact.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Popup Maker - Boost Sales, Conversions, Optins, Subscribers with the Ultimate WP Popup Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via post_title in all versions up to, and including, 1.24.0 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 requires the attacker to create a post with an HTML entity-encoded payload in the title, which bypasses sanitize_text_field on save and is later decoded and executed by the browser when rendered by the Select2 component.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
VulDB
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.
More in Wordpress Plugin
View allThe 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 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
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
Exploit-DB