Security readout for executives and security teams
Plain-English summary
This issue affects the Sygnoos Popup Builder WordPress plugin version 4.1.0 and earlier. A malicious site could potentially cause a user’s browser to change a popup’s status without that user intending it. The documented impact is limited to popup status changes, not full site takeover or data theft.
Executive priority
Treat this as a routine but real web governance issue. It is not currently evidenced as actively exploited, but affected sites should be updated because the flaw can alter customer-facing popup behavior and reduce trust in site operations.
Technical view
CVE-2022-32289 is a CSRF weakness in Popup Builder for WordPress <= 4.1.0. The CVSS 3.1 score is 5.4, with network reachability, low complexity, required user interaction, and low integrity and availability impact. The source bundle does not define the exact affected endpoint or required WordPress role.
Likely exposure
Exposure is limited to WordPress sites running Sygnoos Popup Builder version 4.1.0 or earlier. Highest concern is sites where administrators or content managers remain logged into WordPress while browsing external content.
Exploitation context
The provided sources do not show active exploitation, and the CVE is not marked KEV. Exploitation requires user interaction and appears to affect popup status rather than confidentiality. Evidence is incomplete on exploit maturity and role requirements.
Researcher notes
The public bundle confirms CWE-352, affected versions <= 4.1.0, and impact limited to popup status change. It does not provide endpoint details, proof of exploitation, a named fixed version, or role prerequisites. Avoid assuming broader WordPress compromise.
Mitigation direction
- Inventory WordPress sites for Popup Builder installations and versions.
- Update Popup Builder beyond the affected range using vendor guidance.
- Disable or remove the plugin where it is unused.
- Review WordPress hardening guidance for CSRF and admin session hygiene.
- Monitor vendor and Patchstack advisories for any clarified fixed version.
Validation and detection
- Confirm whether Popup Builder is installed on each WordPress site.
- Verify no site is running Popup Builder version 4.1.0 or earlier.
- Review popup configuration history for unexpected enable or disable changes.
- Check vendor release notes for CSRF-related fixes after 4.1.0.
- Document compensating controls if immediate update is unavailable.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-352: 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.
Open ATT&CK lookupCVE-2022-32289 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L2.82.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://wordpress.org/plugins/popup-builder/#developersCVE reference · x_refsource_CONFIRM
- https://patchstack.com/database/vulnerability/popup-builder/wordpress-popup-builder-plugin-4-1-0-cross-site-request-forgery-csrf-vulnerability-leading-to-popup-status-changeCVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.