WordPress Popup Builder 3.49 contains a persistent cross-site scripting vulnerability that allows authenticated attackers to inject malicious scripts by breaking out of option tags in the post_title parameter. Attackers can submit crafted POST requests to the post.php endpoint with script payloads in the post_title field that execute when pages or posts display popup selections.
Security readout for executives and security teams
Plain-English summary
Popup Builder 3.49 for WordPress can store attacker-supplied script in popup-related content. If an authenticated attacker can create or edit relevant content, the script may run later when popup selections are displayed, potentially stealing session data or changing page behavior.
Executive priority
Treat this as a moderate-priority website integrity risk. It is not unauthenticated remote code execution, but stored XSS can affect administrators or visitors and may support account compromise or reputational damage.
Technical view
The issue is persistent cross-site scripting in Popup Builder 3.49. The source bundle says attackers can break out of option tags through the post_title parameter, causing script execution when affected popup selection UI is rendered. CVSS 3.1 is 5.4, with low privileges required and user interaction required.
Likely exposure
Exposure appears limited to WordPress sites running Popup Builder version 3.49, especially where low-privileged authenticated users can submit or modify popup-related posts. The provided sources do not list other affected versions.
Exploitation context
The bundle includes an ExploitDB reference, so public exploit information exists. However, KEV status is false, and the supplied sources do not establish active exploitation in the wild.
Researcher notes
Evidence supports Popup Builder 3.49 only. The CVE metadata, VulnCheck advisory, and ExploitDB reference align on persistent XSS. Sources do not provide confirmed active exploitation, a named fixed version, or broader version range.
Mitigation direction
Identify WordPress sites running Popup Builder version 3.49.
Check the vendor and WordPress plugin pages for current remediation guidance.
Upgrade to a vendor-supported fixed version if one is documented.
Disable or remove Popup Builder where no supported fix is available.
Limit content-editing privileges to trusted users until remediated.
Validation and detection
Confirm installed Popup Builder versions across WordPress environments.
Review whether untrusted users can create or edit popup-related content.
Check affected content titles for suspicious script-like markup.
After remediation, verify popup selection UI renders titles safely.
Monitor WordPress audit logs for unusual authenticated content changes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-79 · source CWE mapping
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.