Event Espresso 4 Decaf: Cross-site request forgery

Event Espresso 4 Decaf is affected by cross-site request forgery. The vulnerable path is reachable without authentication. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.

CVE / CNA score 4.3 CVSS 3.1 · security@wordfence.com

NVD score Pending NVD has not published its own CVSS assessment.

Component: Event Espresso 4 Decaf
Plugin slug: event-espresso-4-decaf
Affected: See vendor advisory
Safe version: See mitigation notes
Published: Jul 01, 2023
Weakness: CWE-352 — Cross-Site Request Forgery (CSRF)

This CVE was published Jul 01, 2023 and is one of 1 known issue for this plugin.

What to do

Update, patch or deactivate.

Update Event Espresso 4 Decaf to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

The Event Espresso 4 Decaf plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 4.10.11. This is due to missing or incorrect nonce validation on the ajaxHandler() function. This makes it possible for unauthenticated attackers to op into notifications via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

References

Update, patch or deactivate.

Technical description

Primary and upstream sources