Monthly
PHP Object Injection in the Kirki WordPress plugin through 6.3.2 allows an authenticated Editor-level user to submit serialized data to the template import endpoint, but real impact is conditional on another installed plugin or theme providing a usable POP chain. Kirki itself contains no gadget chain, so the flaw alone does not enable file deletion, data theft, or code execution; the supplied 7.2 score overstates immediate risk, and no public exploit was identified at time of analysis. By default, KIRKI_USERS_DEFAULT_FULL_ACCESS lets Editors reach the endpoint despite the PR:H vector.
PHP object injection in the Gravity Forms WordPress plugin (all versions before 3.1.1) allows unauthenticated, network-reachable attackers to feed crafted serialized data into a PHP unserialize() call, which can lead to object injection and, if a suitable gadget chain is present in the running PHP stack, to full compromise of confidentiality, integrity, and availability. The flaw is rated CVSS 8.1 with vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, meaning no credentials and no user interaction are needed, but the high attack-complexity component reflects that exploitation depends on a usable POP gadget chain existing in the plugin, WordPress core, or another installed plugin or theme. At time of analysis there is no public exploit identified (no CISA KEV listing and no published proof-of-concept in the supplied intelligence), and the vulnerability was reported through Patchstack to the vendor, with version 3.1.1 identified as the fixed release.
Unauthenticated PHP object injection in the WordPress plugin Sunshine Photo Cart (all versions up to and including 3.7.4) allows an attacker to store a crafted serialized payload through the plugin's public favorites page, which is then deserialized when any image in a non-viewable or private gallery is viewed. The plugin ships no usable POP gadget chain of its own, so the flaw has no impact on a site running only this plugin; impact materialises only when a separate plugin or theme on the same installation provides a chain, in which case the attacker could delete arbitrary files, retrieve sensitive data, or execute code depending on that chain. No public exploit code or confirmed active exploitation was identified at time of analysis, and while the submitted CVSS is 9.8 the mandatory external gadget-chain precondition means our independent assessment rates it AV:N/AC:H/PR:N/UI:N with high confidentiality, integrity, and availability impact when the precondition is met.
PHP object injection in the Search Regex WordPress plugin version 3.5 lets an authenticated attacker with subscriber-level access or above pass crafted serialized data into the plugin's replace_all function, which is then deserialized by PHP without validation. When a usable POP gadget chain exists in the installed plugin, WordPress core, or another active plugin, this object injection can be escalated to arbitrary code execution, giving the attacker full control of the site. No public exploit code or confirmed in-the-wild exploitation was identified at the time of analysis, and exploitation is conditional on both an authenticated account and a viable gadget chain.
Arbitrary code execution in the Lenovo Legion Zone application allows an attacker positioned on the same logical network (shared LAN or Wi-Fi segment) to run code of their choosing on the affected host. Exploitation requires the attacker to already hold low-level privileges on the network (CVSS PR:L), needs no user interaction, and can affect confidentiality, integrity, and availability - reflected in the reported CVSS 4.0 base score of 8.6 (assessed as CVSS 3.1 8.2-equivalent, AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The issue is a moderate-to-high severity but realistically constrained problem, because Legion Zone is distributed exclusively in the Chinese market and the attack surface is limited to adjacent-network reachability; no public exploit has been identified at time of analysis and the vulnerability is not listed in CISA KEV.
Unauthenticated denial of service in LightLLM through 1.2.0 lets any remote attacker who can reach the /generate endpoint take down the inference worker with a single crafted request: supplying the internal pd_kv_trans_params field causes a pickle.loads failure in InferSamplingParams that kills the inference thread. Because the /health endpoint keeps responding normally, monitoring will not detect the failure, and every subsequent request hangs until the process is restarted. Publicly available exploit code exists (referenced in the upstream GitHub issue), and no CISA KEV entry or EPSS data was provided; the assessed impact is availability-only with no confidentiality or integrity loss.
Authenticated Dolibarr users with privileges to write extrafields, export configurations, or blocked log entries can trigger PHP object injection in versions before 23.0.4, potentially leading to code execution or file manipulation if a suitable gadget chain exists. The flaw resides in jsonOrUnserialize() and requires the stored payload to be non-JSON so that unserialize() runs without class restrictions; exploitation is high-complexity and no public exploit has been identified. Upgrading to 23.0.4 or later is the only complete fix.
Native code execution inside the shim zygote process is possible in runwasi's containerd-shim-wasmtime-v1 prior to 0.6.1 when a victim pulls and runs an attacker-crafted OCI image whose single Wasm layer is actually Wasmtime precompiled (serialized native-code) bytes. Because the shim trusts precompiled-format bytes from image layers as if they came from the trusted precompile-cache path, it deserializes them without normal WebAssembly validation, yielding the filesystem, environment, credentials, networking, and Linux syscall access of the workload container; the escape reaches the workload container boundary but does not by itself break container isolation or give direct host code execution. Per the CVSS vector the attack is network-reachable with no privileges (PR:N), though the independent assessment notes required user interaction (UI:R) to induce the victim to run the image; no public exploit code or confirmed in-the-wild exploitation was identified at time of analysis, and the issue is fixed in 0.6.1.
Amazon Neptune engine versions prior to 1.5.0.0 contain a deserialization flaw in the Gremlin graph data import component that lets an authenticated remote actor holding standard database permissions execute arbitrary code and reach internal service credentials. Exploitation requires working database credentials and network access to the Gremlin import interface, so exposure is greatest in multi-user, multi-tenant, or lower-trust deployments where untrusted parties hold standard DB accounts; no public exploit code or confirmed active exploitation was identified at time of analysis, but the high CVSS 4.0 score (9.4) and our independent CVSS 3.1 assessment (8.8, scope-changed, high confidentiality/integrity/availability impact) confirm this is a genuine high-priority issue rather than a CVSS-inflated one. Vendor-released patches are available as engine version 1.5.0.0 with backports to 1.4.8.1 and 1.4.7.1, and clusters enrolled in auto-update may be remediated without operator action.
Remote code execution affects JetBrains TeamCity releases older than 2026.2, 2026.1.4, and 2025.11.8, where a type-whitelist bypass in the build messages protocol lets a serialized payload cross the deserialization trust boundary and execute code in the server process; the flaw carries a CVSS of 9.8 (AV:N/AC:L/PR:N/UI:N, unauthicated per the PR:N vector). There is no public exploit identified at time of analysis, CISA's SSVC records Exploitation as 'none' with Automatable set to 'no', and EPSS is low at 0.38% (31st percentile), though Technical Impact is rated 'total'. JetBrains has released fixes, so the primary risk is unpatched, network-reachable TeamCity servers whose agent-facing build messages channel is exposed beyond trusted build-agent hosts.
PHP Object Injection in the Kirki WordPress plugin through 6.3.2 allows an authenticated Editor-level user to submit serialized data to the template import endpoint, but real impact is conditional on another installed plugin or theme providing a usable POP chain. Kirki itself contains no gadget chain, so the flaw alone does not enable file deletion, data theft, or code execution; the supplied 7.2 score overstates immediate risk, and no public exploit was identified at time of analysis. By default, KIRKI_USERS_DEFAULT_FULL_ACCESS lets Editors reach the endpoint despite the PR:H vector.
PHP object injection in the Gravity Forms WordPress plugin (all versions before 3.1.1) allows unauthenticated, network-reachable attackers to feed crafted serialized data into a PHP unserialize() call, which can lead to object injection and, if a suitable gadget chain is present in the running PHP stack, to full compromise of confidentiality, integrity, and availability. The flaw is rated CVSS 8.1 with vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, meaning no credentials and no user interaction are needed, but the high attack-complexity component reflects that exploitation depends on a usable POP gadget chain existing in the plugin, WordPress core, or another installed plugin or theme. At time of analysis there is no public exploit identified (no CISA KEV listing and no published proof-of-concept in the supplied intelligence), and the vulnerability was reported through Patchstack to the vendor, with version 3.1.1 identified as the fixed release.
Unauthenticated PHP object injection in the WordPress plugin Sunshine Photo Cart (all versions up to and including 3.7.4) allows an attacker to store a crafted serialized payload through the plugin's public favorites page, which is then deserialized when any image in a non-viewable or private gallery is viewed. The plugin ships no usable POP gadget chain of its own, so the flaw has no impact on a site running only this plugin; impact materialises only when a separate plugin or theme on the same installation provides a chain, in which case the attacker could delete arbitrary files, retrieve sensitive data, or execute code depending on that chain. No public exploit code or confirmed active exploitation was identified at time of analysis, and while the submitted CVSS is 9.8 the mandatory external gadget-chain precondition means our independent assessment rates it AV:N/AC:H/PR:N/UI:N with high confidentiality, integrity, and availability impact when the precondition is met.
PHP object injection in the Search Regex WordPress plugin version 3.5 lets an authenticated attacker with subscriber-level access or above pass crafted serialized data into the plugin's replace_all function, which is then deserialized by PHP without validation. When a usable POP gadget chain exists in the installed plugin, WordPress core, or another active plugin, this object injection can be escalated to arbitrary code execution, giving the attacker full control of the site. No public exploit code or confirmed in-the-wild exploitation was identified at the time of analysis, and exploitation is conditional on both an authenticated account and a viable gadget chain.
Arbitrary code execution in the Lenovo Legion Zone application allows an attacker positioned on the same logical network (shared LAN or Wi-Fi segment) to run code of their choosing on the affected host. Exploitation requires the attacker to already hold low-level privileges on the network (CVSS PR:L), needs no user interaction, and can affect confidentiality, integrity, and availability - reflected in the reported CVSS 4.0 base score of 8.6 (assessed as CVSS 3.1 8.2-equivalent, AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The issue is a moderate-to-high severity but realistically constrained problem, because Legion Zone is distributed exclusively in the Chinese market and the attack surface is limited to adjacent-network reachability; no public exploit has been identified at time of analysis and the vulnerability is not listed in CISA KEV.
Unauthenticated denial of service in LightLLM through 1.2.0 lets any remote attacker who can reach the /generate endpoint take down the inference worker with a single crafted request: supplying the internal pd_kv_trans_params field causes a pickle.loads failure in InferSamplingParams that kills the inference thread. Because the /health endpoint keeps responding normally, monitoring will not detect the failure, and every subsequent request hangs until the process is restarted. Publicly available exploit code exists (referenced in the upstream GitHub issue), and no CISA KEV entry or EPSS data was provided; the assessed impact is availability-only with no confidentiality or integrity loss.
Authenticated Dolibarr users with privileges to write extrafields, export configurations, or blocked log entries can trigger PHP object injection in versions before 23.0.4, potentially leading to code execution or file manipulation if a suitable gadget chain exists. The flaw resides in jsonOrUnserialize() and requires the stored payload to be non-JSON so that unserialize() runs without class restrictions; exploitation is high-complexity and no public exploit has been identified. Upgrading to 23.0.4 or later is the only complete fix.
Native code execution inside the shim zygote process is possible in runwasi's containerd-shim-wasmtime-v1 prior to 0.6.1 when a victim pulls and runs an attacker-crafted OCI image whose single Wasm layer is actually Wasmtime precompiled (serialized native-code) bytes. Because the shim trusts precompiled-format bytes from image layers as if they came from the trusted precompile-cache path, it deserializes them without normal WebAssembly validation, yielding the filesystem, environment, credentials, networking, and Linux syscall access of the workload container; the escape reaches the workload container boundary but does not by itself break container isolation or give direct host code execution. Per the CVSS vector the attack is network-reachable with no privileges (PR:N), though the independent assessment notes required user interaction (UI:R) to induce the victim to run the image; no public exploit code or confirmed in-the-wild exploitation was identified at time of analysis, and the issue is fixed in 0.6.1.
Amazon Neptune engine versions prior to 1.5.0.0 contain a deserialization flaw in the Gremlin graph data import component that lets an authenticated remote actor holding standard database permissions execute arbitrary code and reach internal service credentials. Exploitation requires working database credentials and network access to the Gremlin import interface, so exposure is greatest in multi-user, multi-tenant, or lower-trust deployments where untrusted parties hold standard DB accounts; no public exploit code or confirmed active exploitation was identified at time of analysis, but the high CVSS 4.0 score (9.4) and our independent CVSS 3.1 assessment (8.8, scope-changed, high confidentiality/integrity/availability impact) confirm this is a genuine high-priority issue rather than a CVSS-inflated one. Vendor-released patches are available as engine version 1.5.0.0 with backports to 1.4.8.1 and 1.4.7.1, and clusters enrolled in auto-update may be remediated without operator action.
Remote code execution affects JetBrains TeamCity releases older than 2026.2, 2026.1.4, and 2025.11.8, where a type-whitelist bypass in the build messages protocol lets a serialized payload cross the deserialization trust boundary and execute code in the server process; the flaw carries a CVSS of 9.8 (AV:N/AC:L/PR:N/UI:N, unauthicated per the PR:N vector). There is no public exploit identified at time of analysis, CISA's SSVC records Exploitation as 'none' with Automatable set to 'no', and EPSS is low at 0.38% (31st percentile), though Technical Impact is rated 'total'. JetBrains has released fixes, so the primary risk is unpatched, network-reachable TeamCity servers whose agent-facing build messages channel is exposed beyond trusted build-agent hosts.