Security readout for executives and security teams
Plain-English summary
This flaw lets a logged-in low-privilege WordPress user delete popup content created by the WP Popup Builder plugin. It is not described as data theft or full site takeover, but it can disrupt marketing, newsletter, or conversion workflows that depend on popups.
Executive priority
Treat this as a moderate operational integrity issue. Prioritize sites where popups drive revenue, lead capture, compliance notices, or customer communications, especially if public registration is enabled.
Technical view
CVE-2022-2405 is an authorization and CSRF weakness in a WP Popup Builder AJAX action. The sources state that authenticated users, including subscribers, can delete arbitrary popups. The listed CWEs are CWE-352 and CWE-862, with CVSS 3.1 score 4.3.
Likely exposure
Exposure is limited to WordPress sites using WP Popup Builder in the affected version range. The source bundle has inconsistent version wording, so confirm installed versions against CVE and WPScan records.
Exploitation context
The bundle does not show CISA KEV listing or cited active exploitation. Exploitation requires an authenticated WordPress account, such as subscriber-level access, and impacts integrity by deleting popup records.
Researcher notes
The provided data identifies missing authorization and CSRF checks in an AJAX action but does not include exploit details or a definitive fixed-version statement. The affected version wording should be verified before declaring scope.
Mitigation direction
- Check WPScan and vendor guidance for the corrected plugin version.
- Update or disable WP Popup Builder if your installed version is affected.
- Restrict untrusted subscriber-level accounts until remediation is complete.
- Review backups for restoring deleted popup content if needed.
Validation and detection
- Inventory WordPress sites using WP Popup Builder.
- Compare installed plugin versions with the CVE and WPScan affected range.
- Review WordPress user roles for unnecessary subscriber accounts.
- Check popup records and audit logs for unexpected deletions.
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 lookupCWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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-2405 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
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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:L/UI:N/S:U/C:N/I:L/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://wpscan.com/vulnerability/50037028-2790-47ee-aae1-faf0724eb917CVE reference · x_refsource_MISC
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.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.