Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
MediumPublic exploit

Stored XSS in WordPress Popup Builder

IdentifiersCVE-2023-6000CWE-79· Improper Neutralization of Input…

CVE-2023-6000 affects the Popup Builder WordPress plugin before version 4.2.3. The plugin does not properly restrict low-privilege or unauthenticated/simple visitors from updating existing popup content, and it allows injection of raw JavaScript into those popups. This access control failure combined with insufficient neutralization of script content enables a stored cross-site scripting condition: attacker-supplied JavaScript is saved in popup content and later executed in victims' browsers when the modified popup is rendered.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an attacker to persist malicious JavaScript in popup content on affected WordPress sites. When administrators or site visitors load a page that renders the compromised popup, the injected script executes in their browser in the security context of the vulnerable site. This can enable session theft, nonce or credential harvesting, forced actions as the victim, defacement, malicious redirects, delivery of further payloads, and broader compromise of the WordPress site depending on the victim's privileges.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, disable the Popup Builder plugin or restrict access to popup management functionality until the update can be applied. Monitor for unexpected changes to popup definitions and block or sanitize untrusted script content where possible. Deploy a strong Content Security Policy to reduce XSS impact, and use web application monitoring or file/content integrity checks to detect unauthorized popup updates. These measures are compensating controls and do not replace upgrading to a fixed version.

Remediation

Patch, then assume compromise.

Update the Popup Builder WordPress plugin to version 4.2.3 or later, which addresses the issue. Review existing popups for unauthorized modifications or embedded script content, remove any malicious JavaScript, and audit WordPress accounts, sessions, and site content for signs of follow-on compromise. If exploitation is suspected, rotate administrator credentials, invalidate active sessions, and inspect the site for additional malware or persistence mechanisms.
PUBLIC EXPLOITS

Exploits

No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.

VALID 0 / 1 TOTALView more in app

All candidate exploits were filtered out by Mallory's validation.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
SygnoosPopup Builderapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware1

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity3

Community discussion across Reddit, Mastodon, and other social sources.