Security readout for executives and security teams
Plain-English summary
A WordPress site using Popup Builder 4.1.11 or older could have plugin settings changed if an attacker tricks a logged-in site administrator into taking an action. This is not a server takeover by itself, but unauthorized settings changes can affect site behavior and trust.
Executive priority
Treat as a moderate WordPress hygiene issue. Prioritize internet-facing or business-critical sites using Popup Builder, especially where marketing popups affect customer trust, consent flows, or user redirection.
Technical view
CVE-2022-29495 is a CWE-352 CSRF flaw in Sygnoos Popup Builder for WordPress through 4.1.11. The published CVSS 3.1 score is 5.4, with network access, low attack complexity, no attacker privileges, and required user interaction.
Likely exposure
Exposure is limited to WordPress sites with the Sygnoos Popup Builder plugin installed at version 4.1.11 or earlier.
Exploitation context
The bundle does not show CISA KEV listing or active exploitation evidence. Successful abuse likely depends on social engineering a logged-in WordPress user with permission to change plugin settings.
Researcher notes
Evidence supports CSRF leading to plugin settings update only. The bundle does not provide endpoint detail, proof-of-concept status, fixed version, or exploitation telemetry, so validation should stay focused on version exposure and configuration integrity.
Mitigation direction
- Inventory WordPress sites for Popup Builder plugin usage.
- Upgrade Popup Builder beyond affected versions if vendor guidance confirms a fixed release.
- Review current plugin settings for unauthorized or unexpected changes.
- Limit WordPress administrator access to trusted users.
- Check vendor and WordPress plugin pages for current remediation guidance.
Validation and detection
- Confirm installed Popup Builder versions across all WordPress properties.
- Check whether any site runs version 4.1.11 or earlier.
- Review WordPress audit logs for recent Popup Builder settings changes.
- Verify administrators use current browser and session security controls.
- Document remediation status for each affected site.
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-29495 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:L/I:L/A:N
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:L/I:L/A:N2.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:L/I:L/A:N
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-11-cross-site-request-forgery-csrf-leading-to-plugin-settings-updateCVE 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.