GoodMeet <= 1.1.8 - Cross-Site Request Forgery to Google Meet Credential Reset via 'goodmeet_reset_google_meet_credential'
Strategic Overview
- Status
- Patched in 1.1.9
- Affected Version
<= 1.1.8- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2026-6440
At a glance
CVE-2026-6440 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the GoodMeet WordPress plugin, affecting versions <= 1.1.8. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.1.9; sites on affected versions should update now. Disclosed July 2026, reported by Legion Hunter.
Vulnerability Overview
The GoodMeet – Google Meet Integration for Webinar, Meeting & Video Conference plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to and including 1.1.8. This is due to a missing nonce verification in the reset_credential() function, which handles the wp_ajax_goodmeet_reset_google_meet_credential AJAX action. While the function does verify the user's capability (manage_options), it does not validate a nonce, making it susceptible to CSRF attacks. This makes it possible for unauthenticated attackers to trick a site administrator into clicking a malicious link that will reset (delete) the plugin's stored Google Meet API credentials (goodmeet_google_credentials) and OAuth tokens (goodmeet_google_token), effectively disabling the Google Meet integration on the site.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
GoodMeet <= 1.1.8 carries this weakness at reset_credential(), and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For GoodMeet the fix is 1.1.9: builds <= 1.1.8 are affected, anything from 1.1.9 onward is not.
Remediation
Update to version 1.1.9, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to GoodMeet: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: GoodMeet 1.1.9 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C