Groundhogg: A security weakness

Groundhogg is affected by a security weakness. Exploitation requires an authenticated WordPress account. The resulting impact depends on how the affected component exposes the vulnerable operation.

CVE / CNA score 4.3 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-862 — Missing Authorization

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 unauthorized modification of data due to a missing capability check on the 'submit_ticket' function in versions up to, and including, 2.7.9.8. This makes it possible for authenticated attackers to create a support ticket that sends the website's data to the plugin developer, and it is also possible to create an admin access with an auto login link that is also sent to the plugin developer with the ticket. It only works if the plugin is activated with a valid license.

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

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

References

Update, patch or deactivate.

Technical description

Primary and upstream sources