Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach plugin form endpoint unauthenticated
-
DeliverySubmit crafted serialized PHP object
-
ExploitTrigger unserialize() object injection
-
ExecutionPOP gadget chain executes
-
ImpactCode execution or data compromise
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V1 - Encoding and Sanitization Safe deserialization, type allowlists
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires that the Conversational Forms for ChatBot plugin (version ≤1.5.1) be installed and active on a WordPress site, and that a reachable code path passes attacker-controlled input to PHP unserialize(). Per the CVSS vector (PR:N/UI:N), no authentication or user interaction is required and the attack is remote. The key LIMITING factor not captured by CVSS is the PHP Object Injection prerequisite: successful exploitation beyond the injection itself depends on a usable POP gadget chain existing in the plugin, WordPress core, or another installed component - absent such a chain, impact may be limited to denial of service or be non-exploitable. No plugin-specific feature toggle or non-default configuration is named in the Description. |
| Impact | The input CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 9.8) describes an unauthenticated, network-reachable, low-complexity flaw with full confidentiality, integrity and availability impact - the classic profile of a critical pre-auth RCE-class WordPress plugin bug. However, several real-world risk signals are MISSING from the input: there is no EPSS score, no CISA KEV listing, and no indication of public exploit code. CWE-502 PHP Object Injection vulnerabilities are a nuance here: raw CVSS routinely rates them 9.8, but practical impact depends on whether an exploitable POP (property-oriented programming) gadget chain is reachable in the plugin, WordPress core, or another installed plugin - Patchstack frequently notes that no known POP chain exists, which would make C:H/I:H/A:H aspirational rather than demonstrated. No such gadget-chain detail is provided in this input, so the 9.8 should be treated as an upper bound, not a confirmed end-to-end compromise. Net: this is a genuine priority to patch given the pre-auth network vector and the dangerous CWE class, but in the absence of EPSS, KEV, or POC data the 9.8 likely overstates immediately weaponizable risk - treat as high-priority-patch rather than confirmed under-attack. |
| Exploit ScenarioDerived | An unauthenticated attacker sends a crafted request to a WordPress site running Conversational Forms for ChatBot (≤1.5.1), supplying a malicious serialized PHP object to a form-handling endpoint that calls unserialize() on attacker-controlled input. If a usable POP gadget chain is present in the stack, deserialization triggers it to achieve code execution, file operations, or data tampering. No public proof-of-concept is identified at time of analysis, and real impact is contingent on an available gadget chain. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 18, 2026
PHP object injection in the Conversational Forms for ChatBot WordPress plugin through 1.5.1 allows unauthenticated remote attackers to pass attacker-controlled serialized data into PHP unserialize(), with the potential for full confidentiality, integrity, and availability impact only if a usable POP gadget chain exists in the plugin, WordPress core, or another installed component. The independent assessment scores this as CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H because the high-complexity prerequisite is a viable gadget chain, and the provided data contains no public exploit or CISA KEV confirmation.
RemediationAI
No vendor-released patch version is specified in the provided data; the advisory covers Conversational Forms for ChatBot through 1.5.1, so check the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/conversational-forms/vulnerability/wordpress-conversational-forms-for-chatbot-plugin-1-5-1-php-object-injection-vulnerability?_s_id=cve for an updated release and upgrade as soon as a fixed version is published. If the plugin cannot be updated immediately, deactivate and remove it when chatbot forms are not business-critical, which eliminates the vulnerable code path but removes that functionality. As a compensating control, restrict access to the plugin's form-processing endpoints with a web application firewall or server-level allow/deny rules, accepting that virtual patching may not cover every reachable code path and can be bypassed. Reduce gadget-chain availability by removing unused plugins and themes and by monitoring installed components for known POP chains, understanding that this lowers but does not eliminate exploitation risk.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected code is the WordPress plugin conversational-forms (Conversational Forms for ChatBot), versions through 1.5.1, which handles untrusted input in a way that reaches PHP's unserialize() function. CWE-502 (Deserialization of Untrusted Data) describes the root cause: serialized attacker input is converted into PHP objects without sufficient restriction, enabling PHP Object Injection. Exploitation is not simply a matter of sending a payload; the attacker must find a POP (property-oriented programming) gadget chain whose magic methods such as __wakeup or __destruct perform sensitive actions. That dependency is reflected in the independent assessment's AC:H rating and means impact may be limited to denial of service or be non-exploitable if no chain is present. No CPE strings were supplied, but the Patchstack reference identifies the WordPress plugin and version range.
Know when Wordpress Plugin gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Remote and unauthenticated (AV:N/PR:N/UI:N), but AC:H because PHP object injection realistically requires a suitable POP gadget chain to achieve the high C/I/A impact.
Primary rating from Vendor (patchstack).
CVSS VectorVendor: patchstack
DescriptionCVE.org
Deserialization of Untrusted Data vulnerability in QuantumCloud Conversational Forms for ChatBot conversational-forms allows Object Injection.This issue affects Conversational Forms for ChatBot: from n/a through 1.5.1.
Articles & Coverage 1
Executive ViewAI
Any WordPress site running the Conversational Forms for ChatBot plugin at version 1.5.1 or earlier carries an unauthenticated input-handling flaw that, if fully realized, could expose site data and content and disrupt availability - and no vendor fix has been published. Real-world exploitation is not trivial, since it depends on a usable code chain supplied by the plugin, WordPress core, or another installed component, so practical exposure varies from site to site even though the entry point is internet-facing and requires no credentials. Leadership should treat this as a fleet-wide WordPress hygiene issue, because a compromised site is a direct path to customer data, reputational damage, and any downstream system that trusts the site.
No vendor-released patch identified at time of analysis, so interim mitigations are required: deactivate or remove Conversational Forms for ChatBot 1.5.1 and earlier where the business does not depend on it; otherwise front the plugin's form endpoints with WAF or virtual patching that rejects serialized objects in user-supplied input, restrict and monitor access to those endpoints, and shrink the installed gadget surface by removing unused plugins and themes that could complete a POP chain.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Insecure deserialization occurs when an application converts serialized data (a stream of bytes representing an object's state) back into a living object without proper validation.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
EUVD-2026-103430
GHSA-6959-ggg7-7c9h
NVD
CVE.org
Exploit-DB