Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-4205: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in danieliser Popup Maker – Boost Sales, Conversions, Optins, Subscribers with the Ultimate WP Popups Builder

0
Medium
VulnerabilityCVE-2025-4205cvecve-2025-4205cwe-79
Published: Tue Jun 03 2025 (06/03/2025, 11:22:26 UTC)
Source: CVE Database V5
Vendor/Project: danieliser
Product: Popup Maker – Boost Sales, Conversions, Optins, Subscribers with the Ultimate WP Popups Builder

Description

The Popup Maker plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘popupID' parameter in all versions up to, and including, 1.20.4 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.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/27/2026, 14:21:50 UTC

Technical Analysis

CVE-2025-4205 is a stored Cross-Site Scripting (XSS) vulnerability identified in the Popup Maker plugin for WordPress, developed by danieliser, which is widely used to create popups for marketing and subscriber engagement. The vulnerability exists in all versions up to and including 1.20.4 due to insufficient sanitization and escaping of the 'popupID' parameter during web page generation. This flaw allows authenticated attackers with Contributor-level access or higher to inject arbitrary JavaScript code that is stored persistently and executed in the browsers of users who visit the affected pages. Because the vulnerability is stored XSS, the malicious script can affect multiple users over time, increasing its impact. The CVSS 3.1 base score is 6.4, reflecting a medium severity with network attack vector, low attack complexity, requiring privileges (authenticated Contributor or above), no user interaction, and a scope change. The vulnerability impacts confidentiality and integrity by enabling script execution that can steal session tokens, perform actions on behalf of users, or manipulate page content. No patches are currently linked, and no known exploits have been reported in the wild, but the risk remains significant due to the plugin's popularity and the common presence of Contributor-level users on WordPress sites.

Potential Impact

The impact of CVE-2025-4205 is primarily on the confidentiality and integrity of affected WordPress sites and their users. Exploitation allows attackers to execute arbitrary JavaScript in the context of the vulnerable site, potentially leading to session hijacking, theft of sensitive information, unauthorized actions such as content modification or privilege escalation, and distribution of malware. Because the vulnerability requires only Contributor-level access, attackers who gain or already have such access can leverage this to escalate their influence beyond their intended permissions. This can undermine user trust, damage brand reputation, and lead to regulatory or compliance issues if user data is compromised. The scope of affected systems is broad, given the widespread use of WordPress and the Popup Maker plugin for marketing purposes globally. Although no known exploits are currently active, the vulnerability's presence in a popular plugin makes it a likely target for future attacks.

Mitigation Recommendations

To mitigate CVE-2025-4205, organizations should take the following specific actions: 1) Immediately update the Popup Maker plugin to a patched version once available from the vendor to ensure proper input sanitization and output escaping. 2) Restrict Contributor-level user permissions and audit existing users to minimize the number of accounts that can exploit this vulnerability. 3) Implement Web Application Firewall (WAF) rules to detect and block suspicious payloads targeting the 'popupID' parameter. 4) Conduct regular security reviews and scanning of WordPress plugins to identify and remediate vulnerabilities proactively. 5) Employ Content Security Policy (CSP) headers to limit the execution of unauthorized scripts on the site. 6) Monitor site logs and user activity for unusual behavior indicative of exploitation attempts. 7) Educate site administrators and contributors about the risks of XSS and safe content management practices. These steps go beyond generic advice by focusing on access control, proactive detection, and layered defenses tailored to the nature of this stored XSS vulnerability.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-05-01T20:45:30.799Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 683ee361182aa0cae274169e

Added to database: 6/3/2025, 11:58:25 AM

Last enriched: 2/27/2026, 2:21:50 PM

Last updated: 3/26/2026, 7:44:50 AM

Views: 54

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses