Security readout for executives and security teams
Plain-English summary
This WordPress plugin flaw lets an attacker change Buy Me a Coffee plugin settings if they can trick a site administrator into taking an action, such as following a crafted link. It is not listed in KEV and requires administrator interaction, but the impacted setting changes could affect site integrity, confidentiality, and availability.
Executive priority
Prioritize remediation for public WordPress sites using this plugin, especially where administrators frequently access email or external links from authenticated sessions. Treat as high priority, not emergency, unless local evidence shows compromise.
Technical view
CVE-2023-2079 is a CSRF issue in Buy Me a Coffee – Button and Widget Plugin versions up to and including 3.7. Missing nonce validation affects recieve_post, bmc_disconnect, name_post, and widget_post. The CVSS 3.1 score is 7.1, with network attack vector, low complexity, no privileges, and required user interaction.
Likely exposure
Exposure is limited to WordPress sites running the Buy Me a Coffee – Button and Widget Plugin at version 3.7 or earlier. The source bundle does not identify broader affected products or confirmed exploitation.
Exploitation context
The attacker must cause a logged-in site administrator to perform an action. The vulnerability is not marked in CISA KEV in the provided data, so active exploitation should not be assumed.
Researcher notes
The provided record names vulnerable functions and CSRF root cause, but does not include a detailed patch description or exploitation evidence. Validate nonce and capability protections in the referenced WordPress.org code changes before closing remediation.
Mitigation direction
- Inventory WordPress sites for the Buy Me a Coffee plugin and installed version.
- Update, disable, or remove affected plugin installations according to vendor guidance.
- Restrict administrator browsing and discourage unsolicited links while remediation is pending.
- Review plugin settings for unauthorized changes after exposure windows.
Validation and detection
- Confirm whether the plugin is installed on each WordPress site.
- Verify installed versions are not up to and including 3.7.
- Review administrative activity around plugin settings changes.
- Check vendor or WordPress.org changelog for the CVE-specific fix.
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-2079 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.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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:C/C:L/I:L/A:L2.83.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.1HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/6309258e-e4fc-4edf-a771-2d82a9a85a5c?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/buymeacoffee/trunk/includes/class-buy-me-a-coffee.php?rev=2319979#L162CVE reference
- https://plugins.trac.wordpress.org/browser/buymeacoffee/trunk/admin/class-buy-me-a-coffee-admin.php?rev=2816542CVE reference
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=2935565%40buymeacoffee&new=2935565%40buymeacoffee&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.