Groundhogg: Cross-site request forgery

Groundhogg 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 5.4 CVSS 3.1 · security@wordfence.com

NVD score 4.3 CVSS 3.1 · nvd@nist.gov

Component: Groundhogg
Plugin slug: groundhogg
Affected: See vendor advisory
Safe version: See mitigation notes
Published: May 20, 2023
Weakness: CWE-352 — Cross-Site Request Forgery (CSRF)

This CVE was published May 20, 2023 and is one of 28 known issues for this plugin.

What to do

Update, patch or deactivate.

Update Groundhogg 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 Groundhogg plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.7.9.8. This is due to missing nonce validation on the 'enable_safe_mode' function. This makes it possible for unauthenticated attackers to enable safe mode, which disables all other plugins, via a forged request if they can successfully trick an administrator into performing an action such as clicking on a link. A warning message about safe mode is displayed to the admin, which can be easily disabled.

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

NVD 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