Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify WordPress site running Kalles Addons ≤1.0.6
-
DeliveryFingerprint co-installed plugins and themes for known POP chain providers
-
ExploitCraft serialized PHP payload targeting identified POP chain
-
ExecutionSubmit unauthenticated HTTP request to plugin's deserialization endpoint
-
PersistPHP unserializes payload, triggering magic method chain
-
ImpactAchieve arbitrary file deletion, data exfiltration, or remote code execution
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 two concurrent conditions: (1) the target WordPress site must have the Kalles Addons plugin installed at version 1.0.6 or earlier, and (2) at least one other co-installed plugin or theme must provide a compatible POP chain - a set of exploitable PHP magic methods (__wakeup, __destruct, __toString, etc.) that chain together to produce a dangerous outcome such as file write, file deletion, or code execution. The deserialization call is reachable without authentication (CVSS PR:N, AV:N), but without a POP chain from a secondary component the injection has no impact whatsoever. The exact WordPress input vector - whether a specific POST parameter, REST API endpoint, cookie, or other field - is not disclosed in the available references. Exploitation is bounded by the requirement for a compatible co-installed POP chain provider, which varies entirely by the target site's plugin and theme configuration. |
| Impact | The CVSS 8.1 score (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) accurately models the conditional nature of this vulnerability: the High complexity metric reflects the prerequisite of a co-installed POP chain, absent which there is zero exploitable impact regardless of patch status. A WordPress site running only Kalles Addons 1.0.6 is not exploitable in practice; a site also running a plugin or theme that supplies a POP chain - such as a popular page builder, WooCommerce extension, or form plugin - faces full C:H/I:H/A:H exposure. No EPSS score was provided in the input data; with no KEV listing and no confirmed public exploit code, near-term exploitation probability is assessed as moderate-to-low, concentrated on sites whose plugin stack happens to include a known POP chain source. The unauthenticated network vector means automated mass-scanning for this class of vulnerability is feasible, so even sites with a low perceived profile should treat patching as a routine but non-emergency priority rather than a critical incident response. |
| Exploit ScenarioDerived | An unauthenticated remote attacker sends a crafted HTTP request to the WordPress site containing a serialized PHP payload targeting the Kalles Addons plugin's deserialization point. If a co-installed plugin or theme - such as a popular WooCommerce extension or page builder - exposes a usable POP chain, the deserialized object triggers a chain of PHP magic methods resulting in arbitrary file deletion, credential exfiltration from wp-config.php, or remote code execution under the web server user. No public proof-of-concept exploit has been identified at time of analysis, but the unauthenticated network vector makes automated scanning across large numbers of WordPress sites feasible. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 25, 2026
PHP Object Injection in the Kalles Addons WordPress plugin (all versions up to and including 1.0.6) allows unauthenticated remote attackers to deserialize untrusted PHP objects via a network-accessible deserialization endpoint. Exploitation is strictly conditional: the plugin itself contains no known POP (Property-Oriented Programming) chain, so real-world impact - ranging from arbitrary file deletion and sensitive data retrieval to remote code execution - only materializes when a separately installed plugin or theme on the same WordPress instance supplies a usable POP chain. No public exploit code and no CISA KEV listing have been identified at time of analysis.
RemediationAI
Update the Kalles Addons plugin to any version above 1.0.6 once a patched release is confirmed available - consult the Wordfence advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/46474bf6-0906-4b94-8032-270991c5128d) and the Patchstack entry (https://patchstack.com/database/wordpress/plugin/kalles-addons/vulnerability/wordpress-kalles-addons-plugin-1-0-6-php-object-injection-vulnerability) directly, as no exact fix version is identified in the currently available data. As a compensating control, audit all co-installed plugins and themes for known POP chain providers using a tool such as PHPGGC; disabling or removing any plugin that supplies a POP chain eliminates the exploitability chain without requiring immediate removal of Kalles Addons, though this may affect functionality of those secondary plugins. A WAF rule blocking serialized PHP object payloads (e.g., patterns matching 'O:[0-9]+:' in user-supplied request parameters) can reduce exposure at the cost of potential false positives on legitimate serialized data. If the plugin is not actively used, deactivating and removing it is the lowest-risk interim measure.
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
CWE-502 (Deserialization of Untrusted Data) describes the root cause: the plugin passes user-controlled input to PHP's unserialize() function without sanitization, allowing an attacker to instantiate arbitrary PHP objects. The affected product is identified by CPE cpe:2.3:a:unknown:kalles_addons:*:*:*:*:*:*:*:* and is a WordPress plugin companion, likely bundled with or complementary to a commercial WooCommerce theme. PHP Object Injection exploitability depends entirely on the presence of a POP chain - a sequence of exploitable PHP magic methods (__wakeup, __destruct, __toString, etc.) in already-loaded code that can be chained to produce a dangerous outcome. The deserialization point is reachable without authentication (CVSS PR:N, AV:N), but the CVSS AC:H rating correctly encodes the strict dependency on a co-installed POP chain provider.
Know when Kalles Addons 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:H/PR:N/UI:N/S:U/C:H/I:H/A:H
AC:H correctly captures the mandatory POP chain dependency on a secondary component; PR:N reflects unauthenticated access; C/I/A:H applies conditionally when a POP chain is present.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Kalles Addons plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.0.6 via deserialization of untrusted input. This makes it possible for unauthenticated attackers to inject a PHP Object. No known POP chain is present in the vulnerable software, which means this vulnerability has no impact unless another plugin or theme containing a POP chain is installed on the site. If a POP chain is present via an additional plugin or theme installed on the target system, it may allow the attacker to perform actions like delete arbitrary files, retrieve sensitive data, or execute code depending on the POP chain present.
Executive ViewAI
WordPress sites running Kalles Addons plugin up to version 1.0.6 are susceptible to object injection attacks through unsafe PHP deserialization, which could enable remote code execution or sensitive data compromise. The attack requires an unauthenticated attacker and the co-presence of another vulnerable plugin or theme on the same WordPress instance to provide an exploitable code chain. Organizations should immediately audit WordPress deployments for this combination of vulnerabilities.
Interim mitigations include disabling or removing the Kalles Addons plugin to eliminate the deserialization endpoint, restricting plugin access via Web Application Firewall rules that block POST requests to identified injection endpoints, and implementing continuous monitoring of WordPress application logs for suspicious deserialization or error patterns that may indicate exploitation attempts. Additionally, audit and remove redundant plugins or themes to reduce overall attack surface.
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.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
More in Kalles Addons
View allUnauthenticated PHP Object Injection in the WordPress 'Kalles Addons' plugin (by the4) through version 1.0.6 lets remote
Stored Cross-Site Scripting in the Kalles Addons WordPress plugin (versions <= 1.0.6) allows a low-privileged subscriber
EUVD-2026-65355
GHSA-rm66-h7v3-77rx
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB