Security readout for executives and security teams
Plain-English summary
This flaw lets an attacker trick a WordPress site administrator into triggering a request that disconnects GiveWP's Stripe integration. It does not expose donor data in the source bundle, but it can disrupt donation processing and payment operations for sites using GiveWP with Stripe.
Executive priority
Treat this as a moderate operational risk for donation sites. Prioritize nonprofit, fundraising, and revenue-generating WordPress properties using GiveWP with Stripe, because the likely harm is payment disruption rather than full site compromise.
Technical view
GiveWP up to and including 2.33.3 has a CSRF issue in give_stripe_disconnect_connect_stripe_account due to missing or incorrect nonce validation. A forged request can deactivate Stripe integration settings if an administrator performs attacker-induced interaction. The CVSS 3.1 score is 5.4, with user interaction required.
Likely exposure
Exposure is limited to WordPress sites running GiveWP Donation Plugin and Fundraising Platform versions up to 2.33.3, especially where Stripe is configured for donations. Sites not using GiveWP or not using its Stripe integration are unlikely to have meaningful business impact from this issue.
Exploitation context
The provided sources do not show active exploitation, and the CVE is not listed as KEV. Exploitation requires social engineering of a site administrator. The expected impact is integrity and availability disruption through Stripe integration deactivation, not direct data theft based on the bundle.
Researcher notes
The key condition is CSRF against the Stripe disconnect admin action, tied to nonce validation. The source bundle includes Wordfence, the affected admin action reference, and a WordPress plugin changeset, but does not provide evidence of exploitation in the wild.
Mitigation direction
- Update GiveWP to a vendor-supported release newer than 2.33.3.
- Check vendor and Wordfence guidance for the confirmed fixed version.
- Verify Stripe remains connected after updating GiveWP.
- Warn administrators against unexpected GiveWP or Stripe settings links.
- Monitor donation failures and payment configuration changes.
Validation and detection
- Inventory WordPress sites using GiveWP and record plugin versions.
- Confirm whether each site runs GiveWP 2.33.3 or earlier.
- Check whether GiveWP Stripe integration is enabled.
- Review admin activity around Stripe disconnect or payment setting changes.
- Confirm nonce validation exists in the relevant Stripe admin 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-4248 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/2bff8dea-6971-47d4-bd2c-0821687033e5?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/give/trunk/includes/gateways/stripe/includes/admin/admin-actions.php?rev=2585755#L361CVE 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.