Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privileged user
-
DeliverySubmit crafted serialized payload
-
ExploitTrigger unsafe deserialization
-
ExecutionInstantiate malicious PHP objects via gadget chain
-
ImpactAchieve code execution or file manipulation
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 | Exploitation requires a low-privileged authenticated WordPress account (CVSS PR:L) - typically a subscriber or registered user, which is readily obtainable on sites that permit open user registration. The vulnerable component is the Strong Testimonials plugin at versions up to and including 3.3.12; sites not running this plugin are unaffected. Successful object injection to a high-impact outcome (RCE, file operations) depends on the presence of a usable PHP POP gadget chain in the loaded plugins, themes, or WordPress core - the deserialization itself is the entry point, but meaningful impact is gadget-dependent. No user interaction is required (UI:N), and the vector is network-reachable (AV:N) with low attack complexity (AC:L). The primary limiting factors are the authentication requirement and the environmental availability of exploitable gadgets. |
| Impact | This is a credible high-priority issue but with an important caveat that tempers the raw CVSS 8.8. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) indicates a network-reachable, low-complexity attack requiring only low privileges (PR:L) and no user interaction, with high impact to confidentiality, integrity, and availability - consistent with PHP Object Injection (CWE-502) that can lead to code execution, arbitrary file operations, or data access when a suitable POP gadget chain is present. No EPSS score, KEV listing, or SSVC decision data was provided in the input, so exploitation probability and automatability cannot be quantified from the available signals. No public exploit was identified at time of analysis, so the C/I/A:H impacts represent potential rather than demonstrated outcomes - PHP object injection is only as dangerous as the gadget chains reachable in the victim's loaded code (plugin, themes, or core), which is environment-dependent. The PR:L requirement is the key risk-limiting factor: an attacker needs at least a low-privileged authenticated account (commonly a subscriber/registered user on WordPress sites allowing self-registration), which distinguishes this from a fully unauthenticated mass-exploitable flaw. Net assessment: a real priority for sites running the affected plugin that permit low-privilege account creation, but not a drop-everything internet-wide emergency absent evidence of active exploitation. |
| Exploit ScenarioDerived | An attacker with a low-privileged authenticated WordPress account (e.g., a self-registered subscriber) submits a crafted serialized PHP payload to a vulnerable endpoint in the Strong Testimonials plugin, triggering unsafe deserialization and instantiating attacker-chosen PHP objects. If a usable POP gadget chain exists in the installed plugins, themes, or WordPress core, this object injection can escalate to arbitrary file write/delete, SQL interaction, or remote code execution. No public proof-of-concept was identified at time of analysis. |
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 WP Chill Strong Testimonials WordPress plugin, affecting all versions through 3.3.12, allows a low-privileged authenticated user to pass serialized data into an unsafe deserialization path and potentially instantiate arbitrary PHP objects. Because the CVSS 8.8 vector is PR:L, exploitation first requires a subscriber-level account, which is trivially obtainable on sites with open registration; user interaction is not needed (UI:N) and the attack is network-reachable with low complexity. Real-world impact beyond the injection itself - such as remote code execution or file manipulation - depends on whether a usable POP gadget chain exists in the site's installed themes and plugins, and no public exploit code or confirmed in-the-wild activity (CISA KEV) has been identified at the time of analysis.
RemediationAI
Update the Strong Testimonials plugin to the latest release published after 3.3.12 - the affected range ends at 3.3.12, but the exact fixed version number is not confirmed in the available data, so verify the current version on wordpress.org or in the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/strong-testimonials/vulnerability/wordpress-strong-testimonials-plugin-3-3-12-php-object-injection-vulnerability?_s_id=cve) before rolling out, and use the WordPress admin updater or wp plugin update strong-testimonials to apply it. If an immediate upgrade is not possible, disable or deactivate the plugin where testimonial functionality is not business-critical, which removes the attack surface entirely at the cost of losing the testimonial display and submission features; alternatively, harden the prerequisite by disabling open user registration and auditing existing subscriber accounts, since exploitation requires a low-privileged authenticated session (PR:L), though this only raises the bar rather than closing the flaw. A WAF or virtual patch rule that inspects POST bodies for serialized PHP object payloads (patterns such as O:<length>:"<class>") targeting the plugin's endpoints can provide interim coverage, but it is signature-based and may cause false positives on legitimate serialized form data, and it does not address gadget chains reachable through other request paths. Because the ultimate impact is gadget-dependent, reducing the number of plugins/themes with known POP chains on the site lowers the blast radius of a successful injection.
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 flaw is CWE-502 (Deserialization of Untrusted Data) in a WordPress plugin context. PHP's unserialize() reconstructs objects from attacker-influenced strings and, during reconstruction, automatically invokes magic methods such as __wakeup() and __destruct(); if a class with a dangerous magic method is loaded, the attacker can steer a property-oriented programming (POP) chain toward file writes, SQL execution, or arbitrary code execution. The Strong Testimonials plugin accepts data through WordPress request handling (network-reachable, AV:N) with low attack complexity (AC:L) but requires an authenticated session, as reflected by the PR:L component of the CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H vector. The CVSS scope is unchanged (S:U), meaning the impact is measured against the vulnerable plugin's own security authority, but object injection is inherently environment-dependent: the severity in practice hinges on the gadget inventory of the specific site's plugin and theme stack rather than on the plugin alone. No CPE strings were supplied in the available data, so affected asset identification relies on the vendor product/version range (Strong Testimonials through 3.3.12) rather than formal CPE matching.
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:L/UI:N/S:U/C:H/I:H/A:H
PHP object injection reachable over the network by a low-privileged authenticated user (PR:L) with no interaction; gadget-driven code execution supports C/I/A:H, scope unchanged.
Primary rating from Vendor (patchstack).
CVSS VectorVendor: patchstack
DescriptionCVE.org
Deserialization of Untrusted Data vulnerability in WP Chill Strong Testimonials strong-testimonials allows Object Injection.This issue affects Strong Testimonials: from n/a through 3.3.12.
Executive ViewAI
WP Chill Strong Testimonials, affecting all versions through 3.3.12, exposes WordPress sites to PHP object injection from a low-privileged authenticated subscriber account, with potential for broader site compromise only if a usable gadget chain exists. Because subscriber access is often easy to obtain on sites with open registration and no vendor-released patch is identified at time of analysis, leadership should prioritize exposure reduction. No public exploit identified at time of analysis, but the plugin's unpatched state and common low-privileged access path warrant prompt mitigation.
No vendor-released patch identified at time of analysis; interim mitigations include deactivating or removing Strong Testimonials through 3.3.12 where feasible, restricting or disabling open registration and auditing subscriber accounts, applying WAF/virtual patching for PHP object injection or serialized-data abuse if available, reviewing installed themes/plugins for usable POP gadget chains, and monitoring for suspicious deserialization activity.
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-103433
GHSA-46gq-h347-cfrq
NVD
CVE.org
Exploit-DB