Security readout for executives and security teams
Plain-English summary
This is a CSRF issue in the WordPress Leadster plugin up to version 1.1.2. An attacker may be able to cause an unintended low-impact change if a legitimate user is tricked into interacting with malicious content. The public sources do not show active exploitation.
Executive priority
Treat as a moderate website hygiene issue, not an emergency based on current evidence. Prioritize affected public WordPress sites, especially where administrators frequently access the dashboard from general browsing environments.
Technical view
CVE-2023-47791 is CWE-352 in Leadster for WordPress, reported for versions <= 1.1.2. CVSS 3.1 is 4.3 with network attack vector, low complexity, no privileges required, user interaction required, and low integrity impact only. No vulnerable endpoint, CPE, fixed version, or exploit details are provided in the bundle.
Likely exposure
Exposure is limited to WordPress sites with the Leadster plugin installed at version 1.1.2 or earlier. Sites not using this plugin are not indicated as affected by the provided sources.
Exploitation context
The bundle does not cite KEV listing or active exploitation. The CVSS vector indicates user interaction is required, consistent with CSRF risk where a logged-in user may be induced into an unintended action.
Researcher notes
Public detail is sparse. The bundle identifies CSRF and version <= 1.1.2, but does not provide affected CPEs, request parameters, nonce behavior, exploit status, or a named fixed version. Avoid asserting more without vendor confirmation.
Mitigation direction
- Inventory WordPress sites for the Leadster plugin and version.
- Check Patchstack and vendor guidance for a fixed version or official mitigation.
- Update the plugin if a vendor-supported fixed release is available.
- Disable or remove the plugin where business impact allows until guidance is confirmed.
- Limit WordPress administrative access to trusted users and hardened workstations.
Validation and detection
- Confirm whether Leadster is installed on each WordPress instance.
- Record plugin versions and flag any instance at 1.1.2 or earlier.
- Review vendor or Patchstack advisories for remediation status.
- Review WordPress admin activity for unexpected Leadster-related configuration changes.
- Confirm compensating controls do not rely on an unverified patch claim.
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-2023-47791 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:N/UI:R/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:N/UI:R/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:N/UI:R/S:U/C:N/I:L/A:N
Source materials
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.