CVE-2024-38776

WP GoToWebinar <= 15.7 - Cross-Site Request Forgery to Stored Cross-Site Scripting

2024-07-19 00:00
Majed Refaea

Strategic Overview

Status
Patched in 15.8
Affected Plugin
WP GoToWebinar
Affected Version
<= 15.7
CVSS
6.1Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-38776
View all WP GoToWebinar vulnerabilities

At a glance

CVE-2024-38776 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP GoToWebinar WordPress plugin, affecting versions <= 15.7. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 15.8; sites on affected versions should update now. Disclosed July 2024, reported by Majed Refaea.

Vulnerability Overview

The WP GoToWebinar plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 15.7. This is due to missing or incorrect nonce validation on the wp_gotowebinar_save_authentication_details() function. This makes it possible for unauthenticated attackers to inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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)

WP GoToWebinar <= 15.7 carries this weakness at wp_gotowebinar_save_authentication_details(), 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 WP GoToWebinar the fix is 15.8: builds <= 15.7 are affected, anything from 15.8 onward is not.

Remediation

Update to version 15.8, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WP GoToWebinar: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP GoToWebinar 15.8 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C