Live › vulnerability › CVE-2026-109221
Go to dashboardThe Groundhogg WordPress CRM plugin up to and including 4.9.3 fails to validate file paths in its copy_file function, so an authenticated user can delete arbitrary files on the server. Deleting a file such as wp-config.php can lead to remote code execution.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Sites running the Groundhogg plugin at version 4.9.3 or earlier are exposed. Exploitation needs an account with the import_contacts capability, which the plugin grants by default to its Sales Representative role, so sites without that role or those accounts are not exposed to this path.
No product ranges from the sources yet.
wp plugin get groundhogg --field=version4.9.3Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
The Groundhogg — CRM, Newsletters, and Marketing Automation plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the copy_file function in all versions up to, and including, 4.9.3 This makes it possible for authenticated attackers, with Sales Representative-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). This is exploitable by any user holding the plugin-defined import_contacts capability, which is granted by default to the plugin's custom Sales Representative role.
This page as .md · .json · in your agent: get_signal("CVE-2026-109221")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.