Back Redpacketsecurity CVE Alert: CVE-2026-104010 – creativewerkdesigns – WPSyncSheets For Contact Form 7 – CF7 Google Sheets Connector & Save to Database
The WPSyncSheets For Form 7 – CF7 Google Sheets Connector & Save to Database plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1.8.0 via the ‘any non-system CF7 field (e.g., your-message)’ parameter parameter. This is due to insufficient sanitization of CF7 submission field values before database storage and the absence of an allowed_classes restriction on maybe_unserialize() during admin retrieval. This makes it possible for unauthenticated attackers to execute code on the server. Successful exploitation of the remote code execution gadget chain requires that a Google Sheets access token be configured in the plugin (its primary advertised feature), as this triggers autoloading of the bundled Monolog 2.10.0 library whose classes form the exploitable gadget chain; however, the underlying PHP Object Injection occurs regardless.
**Risk verdict:** High-impact but conditional risk; SSVC reports no exploitation, while KEV, PoC and EPSS status are not supplied, so verify exposure promptly rather than assume active exploitation.
**Why this matters:** A crafted form submission may be stored and later become a route to server-side code execution when an administrator retrieves the entry, potentially exposing site data and credentials. A configured Sheets access token enables the reported gadget chain; without it, the underlying unsafe object handling remains, so its absence does not remove all risk.
**Most likely attack path:** An unauthenticated attacker submits a crafted value through a publicly reachable form; exploitation also depends on a later administrator retrieval and is assessed as difficult to execute. The impact is expected to remain within the affected server’s security scope, but a foothold could enable access to local secrets or connected systems.
**Who is most exposed:** WordPress sites using public Form 7 forms with this connector, especially where submissions are stored and administrators routinely review them or Sheets integration is enabled.
Review form submissions and stored entries for unusual serialized-looking payloads.
Check web and PHP logs for errors or unexpected activity during entry retrieval.
Investigate unexplained outbound connections, new processes or modified files on the web host.
Mitigation and prioritisation:
Check for a vendor-fixed release and upgrade promptly; the supplied data does not identify one.
If no fix is available, disable the connector and prevent access to stored entries.
Temporarily restrict public form submissions where operationally feasible.
Review and rotate exposed credentials, including Google access tokens, after suspected compromise; test changes before broad rollout.
A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.
If you like the site, please support us on Patreon or Buy Me A Coffee using the buttons below.
The full story
This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.
