CVE-2026-104010creativewerkdesigns WPSyncSheets For Contact Form 7 deserialization of untrusted data
CVE-2026-104010 is a deserialization of untrusted data in creativewerkdesigns WPSyncSheets For Contact Form 7, rated high (7.5 on CVSS 3.1).
Why this priority: High severity, with no exploitation signal yet.
Published · Updated · NVD status: Deferred
What it is
Serialized objects from outside are turned back into live objects, which a crafted payload can abuse to run code.
How it is reached
An attacker can exploit it over the network, without an account, but someone has to act first, such as opening a file or following a link. Success also depends on conditions the attacker does not fully control.
What an attacker gains
A successful attack can read the data it protects, change data or behaviour and take it offline. In practice, this kind of flaw lets an attacker turn crafted data into code execution inside the receiving service.
Is it being exploited?
There is no public report of exploitation yet.
What to do
- No fixed version is listed yet. Find every place creativewerkdesigns WPSyncSheets For Contact Form 7 runs, watch the references for a fix, and plan a replacement if it is no longer supported.
- While there is no fix, keep it off the internet or behind a VPN, allowlist or authenticating proxy.
- Warn the people who use it, and filter files and links on the way in.
Description from NVD
The WPSyncSheets For Contact 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.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- WordPress sites and their plugins. Plugins run inside the site with its database access, and many sites are public.
- APIs, queues and caches that accept serialized objects. The flaw sits between a message producer and the service that deserializes it.
Trust boundaries in play
- Internet-facing entry points. No account is needed. Any instance reachable from outside your perimeter, through a load balancer, gateway, VPN or exposed admin port, is in scope.
- People who open files and links. Mail, chat and browsers are the delivery path.
- Between a message producer and the service that deserializes it. An attacker who crosses it can turn crafted data into code execution inside the receiving service.
Questions to answer about your own systems
- Where does creativewerkdesigns WPSyncSheets For Contact Form 7 run in your systems, and at which version?
- Which of those instances can be reached from the internet or partner networks?
- What can it reach once compromised: which data stores, secrets and services?
Read more
Advisories
More reading
- plugins.trac.wordpress.org/browser/contactsheets-lite/tags/1.8.0/includes/class-wpsslc-google-api-functions.php#L157
- plugins.trac.wordpress.org/browser/contactsheets-lite/tags/1.8.0/includes/class-wpsslc-service.php#L114
- plugins.trac.wordpress.org/browser/contactsheets-lite/tags/1.8.0/includes/class-wpsslc-service.php#L184
- plugins.trac.wordpress.org/browser/contactsheets-lite/tags/1.8.0/includes/entry/class-wpsslc-cf7-entries-table.php#L459
- plugins.trac.wordpress.org/browser/contactsheets-lite/tags/1.8.0/includes/entry/class-wpsslc-single-entry.php#L131
- plugins.trac.wordpress.org/changeset/3783292/contactsheets-lite/trunk/includes/entry/class-wpsslc-cf7-entries-table.php
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.