Buy Me a Coffee is a crowdfunding platform that allows creators to accept payments and support from their audience; its vulnerability disclosures center on its web application and reflect typical application-security weaknesses including missing authorization controls, cross-site request forgery, and cross-site scripting. Current severity, exploitation activity, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Buymeacoffee over time
Signals from CVEs in this vendor scope (5 CVEs).
5 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2023-2082MEDIUM The "Buy Me a Coffee – Button and Widget Plugin" plugin for WordPress is vulnerable to Cross-Site Scripting in versions up to, and including, 3.6 due to insufficient sanitization a | Jul 14, 2023 | 5.4 | 19 | NO | NO |
CVE-2023-2079HIGH The "Buy Me a Coffee – Button and Widget Plugin" plugin for WordPress is vulnerable to Cross-Site Request Forgery due to missing nonce validation on the recieve_post, bmc_disconnec | Jul 11, 2023 | 7.1 | 18 | NO | NO |
CVE-2023-2078MEDIUM The "Buy Me a Coffee – Button and Widget Plugin" plugin for WordPress is vulnerable to unauthorized modification of data due to missing capability checks on the recieve_post, bmc_d | Jul 11, 2023 | 4.3 | 16 | NO | NO |
CVE-2023-2578MEDIUM The Buy Me a Coffee WordPress plugin before 3.7 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site | Jul 10, 2023 | 4.8 | 16 | NO | NO |
CVE-2023-25030MEDIUM Missing Authorization vulnerability in Buy Me a Coffee.This issue affects Buy Me a Coffee: from n/a through 3.7. | Jun 12, 2024 | 4.3 | 15 | NO | NO |
Signals from CVEs in this vendor scope (5 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Buymeacoffee.
Media articles that mention a CVE ID that affects a product developed by Buymeacoffee — matched by CVE ID, not by vendor name.