Security readout for executives and security teams
Plain-English summary
Popup Builder for WordPress before 4.2.6 can let a site administrator in a Multisite setup make the server request an attacker-chosen location. That can expose sensitive internal resources or files reachable by the web server. The sources do not show confirmed active exploitation.
Executive priority
Patch or remove affected Popup Builder installations on Multisite WordPress estates promptly. The issue requires privileged access according to the description, but successful abuse could expose sensitive internal data reachable from the server.
Technical view
The flaw is a CWE-918 server-side request forgery issue caused by insufficient validation of a request parameter before the plugin makes an outbound request. The source description scopes abuse to administrator-role users in WordPress Multisite configurations and identifies versions before 4.2.6 as affected.
Likely exposure
Exposure is most likely on WordPress Multisite installations using the Popup Builder plugin below version 4.2.6, especially where many administrators or site administrators exist. Single-site exposure is not established by the provided sources.
Exploitation context
WPScan is cited with an exploit-tagged vulnerability entry, but the bundle does not establish real-world active exploitation, and the CVE is not marked KEV. Treat this as a credible but privilege-scoped SSRF/file-read risk rather than confirmed mass exploitation.
Researcher notes
There is a source tension: the narrative says Admin+ in Multisite, while the bundled CVSS vector lists no privileges required. Do not assume unauthenticated exploitability from the provided evidence. Validate exposure through version inventory and deployment context.
Mitigation direction
- Inventory WordPress sites for Popup Builder and installed plugin versions.
- Update Popup Builder to version 4.2.6 or later where applicable.
- Prioritize Multisite deployments with multiple administrator-level users.
- Review vendor or WPScan guidance before applying compensating controls.
- Restrict administrator privileges to trusted users only.
Validation and detection
- Confirm whether each WordPress deployment uses Multisite.
- Check whether Popup Builder is installed and below 4.2.6.
- Review administrator and site-administrator accounts for unnecessary access.
- Look for unusual outbound server requests around suspected plugin use.
- Document whether vendor remediation was applied or still pending.
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-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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 lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2023-6294 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
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:N/S:U/C:H/I:N/A:N3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://wpscan.com/vulnerability/eaeb5706-b19c-4266-b7df-889558ee2614/CVE reference · exploit, vdb-entry
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.
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.