Security readout for executives and security teams
Plain-English summary
CVE-2023-4247 is a CSRF issue in the GiveWP WordPress plugin up to 2.33.3. If an attacker convinces a logged-in administrator to take a crafted action, the attacker can deactivate the SendWP plugin. Business impact is limited but could disrupt workflows that depend on SendWP.
Executive priority
Treat this as a routine but real WordPress plugin hygiene item. Prioritize sites that rely on GiveWP and SendWP for operational workflows, but do not treat it as emergency-level without evidence of exploitation.
Technical view
The issue is missing or incorrect nonce validation in GiveWP's give_sendwp_disconnect function. The CVSS 3.1 score is 5.4, with required user interaction and low integrity and availability impact. Sources identify CWE-352 and a code changeset associated with remediation.
Likely exposure
Exposure is most likely on WordPress sites running GiveWP version 2.33.3 or earlier, especially where administrators are logged in and SendWP is installed. The provided data does not identify other affected products.
Exploitation context
The CVE is not listed as CISA KEV in the provided bundle, and no cited source states active exploitation. Exploitation requires tricking a site administrator into performing an action, which lowers urgency compared with unauthenticated direct exploitation.
Researcher notes
The core condition is CSRF against give_sendwp_disconnect, not a direct unauthenticated plugin takeover. Research should focus on version confirmation, nonce validation in the patched code path, and whether SendWP deactivation creates operational impact in the specific environment.
Mitigation direction
- Update GiveWP beyond 2.33.3 after confirming vendor guidance.
- Review Wordfence and WordPress plugin change history for the fixed version.
- Confirm the SendWP plugin remains active where business workflows need it.
- Train administrators to avoid unexpected plugin-management links.
- Restrict WordPress admin access to trusted users and networks where practical.
Validation and detection
- Inventory WordPress sites using the GiveWP plugin.
- Check installed GiveWP versions for 2.33.3 or earlier.
- Verify whether SendWP is installed and required on each site.
- Review plugin audit logs for unexpected SendWP deactivation.
- Confirm updated code includes nonce validation for the disconnect action.
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-4247 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://www.wordfence.com/threat-intel/vulnerabilities/id/e32d9104-5a39-4455-b76a-e24ae787bdfd?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/give/trunk/includes/admin/misc-functions.php?rev=2772225#L333CVE reference
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&new=2974851%40give%2Ftrunk&old=2973080%40give%2Ftrunk&sfp_email=&sfph_mail=CVE reference
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.