Deserialization
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.
Unauthenticated access to Apache Kylin's in-house broadcast API combined with polymorphic deserialization of attacker-supplied data exposes Kylin 4.0.0 through 5.0.4 to high-impact compromise of the affected service, assessed as network-reachable without privileges or user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). The vendor classifies the issue as 'moderate' severity but notes that practical risk is concentrated on Kylin instances whose broadcast endpoint is directly reachable from a public network, which Apache describes as 'not common'; typical internal-only deployments are considered largely unimpacted. No CISA KEV entry, EPSS score, or public exploit code was present in the source data, so there is no public exploit identified at time of analysis, and this assessment rests almost entirely on the Apache advisory, which recommends upgrading to Apache Kylin 5.0.5.
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 deserialization in EspoCRM versions prior to 9.3.7 lets an authenticated administrator achieve remote code execution by storing crafted serialized object data in background MassAction or Export parameters that the application later unserializes without any allowed-class restriction. The deserialization sinks are reachable over the network (AV:N) with no user interaction (UI:N), and an attacker with admin credentials can instantiate arbitrary PHP objects and execute code, provided a usable gadget chain is reachable in the deployed codebase or its dependencies. Publicly available exploit code exists, and the vendor released a fix in version 9.3.7; the practical limiting factor is the administrator-privilege prerequisite (PR:H), which tempers real-world urgency even though the flaw is rated 9.1.
PHP object injection in Link Whisper Free (a WordPress plugin) through version 0.9.7 allows unauthenticated remote attackers to pass untrusted data into PHP's unserialize() and instantiate arbitrary objects, per the CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (9.8) supplied with the advisory. Our independent assessment keeps the network-reachable, unauthenticated, no-interaction prerequisites but raises attack complexity to High (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H), because CWE-502 only translates into full confidentiality, integrity, and availability loss when a usable POP gadget chain exists somewhere in the plugin, its bundled libraries, or other code loaded on the target site; absent such a chain the injected object may be inert. No public exploit identified at time of analysis, there is no CISA KEV listing, and no EPSS score was provided, so exposure today is limited to sites running the vulnerable plugin version that also happen to carry a viable gadget chain.
Eclipse Vert.x DB2 Client versions 4.0.0 through 4.5.34, 5.0.0 through 5.0.12, 5.1.0 through 5.1.9, and 5.2.0 can deserialize attacker-controlled DRDA UDT column data, enabling remote code execution if a Java deserialization gadget chain is present on the classpath or denial of service otherwise. The affected component is io.vertx:vertx-db2-client, and exploitation requires an application to connect to a malicious or man-in-the-middle DRDA server that returns a result-set column tagged with FDOCA LID 0x50; legitimate DB2 servers never emit that type, and client-side TLS is disabled by default. The CVSS 4.0 score is 9.2 with PR:N, but practical exploitation requires attacker server-side/MITM position (AC:H) and, for RCE, a classpath gadget chain; no public exploit identified at time of analysis, and the real-world blast radius is narrower than the score alone suggests.
PHP object injection in ILIAS LMS affects installations before 9.24, 10.12, and 11.5, allowing an authenticated user who holds the Test creation or Test import permission to deserialize attacker-controlled objects by importing a crafted Test results archive. By embedding a malicious 'tst_sequence' (sequence) attribute in the archive XML, the attacker reaches an unrestricted unserialize() call and can leverage the bundled Guzzle or Monolog libraries as POP gadget chains to write PHP files and achieve remote code execution on the server. The primary limiting factor is the required authenticated account and import-level permission rather than any anonymous exposure; no public exploit code has been identified at time of analysis and the flaw is not confirmed as actively exploited (no CISA KEV listing).
Unauthenticated PHP object injection in e107 CMS before 2.3.7 lets a remote attacker who can reach install.php execute arbitrary PHP functions with the web server's privileges, resulting in full server compromise (CVSS 3.1 base 9.8, AV:N/AC:L/PR:N/UI:N/C:H/I:H/A:H). The flaw arises because the installer decodes the attacker-controlled previous_steps POST parameter and feeds it to unserialize() without restricting allowed classes, and because install.php remains reachable after a normal installation. No public exploit code was identified at time of analysis and CISA KEV does not list this issue, but the advisory documents a complete, directly usable gadget chain (GuzzleHttp\Psr\7\PumpStream → paths.hash → site_path callable coercion) that makes reliable exploitation realistic for any deployment that left the installer endpoint exposed; sites that deleted or access-restricted install.php after setup are the main mitigating factor.
Denial of service in NASA's F´ (F Prime) framework prior to 4.2.0 allows remote attackers to abort or reset the flight software process by delivering a file-uplink packet whose file-packet type byte falls outside the valid Type enum, driving Fw::FilePacket deserialization into an unvalidated FW_ASSERT (CWE-617). The impact is availability-only, matching the assessed CVSS 3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) with no confidentiality or integrity loss, and the practical limiting factor is reachability: the malicious packet must traverse the Svc::FileUplink file-packet path, which in spaceflight deployments is the ground-to-vehicle uplink. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the vendor has released a fix in F Prime 4.2.0.
Malformed inter-processor hub traffic can abort or reset NASA's F´ (F Prime) flight-software process in versions prior to 4.2.0, because the Svc::GenericHub receive handler treats externally supplied deserialization results as invariants and aborts via FW_ASSERT when they fail. An unauthenticated remote peer on a hub link (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, base 7.5) can send a truncated buffer, a HubType value at or above HUB_TYPE_MAX, or a header-only command-dispatch payload to trigger the fault, producing availability-only impact. The vendor has released 4.2.0 with hardened bounds and type checks; no public exploit code has been identified at time of analysis, and the issue is confined to deployments that genuinely instantiate GenericHub and expose its link to untrusted or spoofable peers.
PHP object injection in the itthinx Affiliates WordPress plugin (all versions through 7.0.1) allows remote, unauthenticated attackers to reach a code path that deserializes attacker-controlled input via unserialize(), which can lead to full object injection against the affected site. The supplied CVSS 3.1 vector scores it 9.8 (AV:N/AC:L/PR:N/UI:N/C:H/I:H/A:H), while our independent assessment applies AC:H because meaningful exploitation depends on the presence of a usable PHP POP gadget chain in the plugin, WordPress core, or another installed plugin/theme; without such a chain the practical effect is usually limited. No public exploit code has been identified at time of analysis, and no CISA KEV listing exists, but sites running Affiliates 7.0.1 or earlier alongside components that expose gadget chains face materially elevated risk.
PHP object injection in the Brainstorm Force SureCart WordPress plugin (all versions through 4.9.3) lets a low-privilege authenticated attacker supply untrusted serialized data that the plugin deserializes, enabling arbitrary object instantiation and, where a usable gadget chain exists in the plugin or its dependencies, escalation to code execution or full site compromise. The CVSS 3.1 base score is 8.8 (High) with vector AV:N/AC:L/PR:L/UI:N and High confidentiality, integrity, and availability impact, and no user interaction is required; exploitation still depends on reaching the specific vulnerable deserialization endpoint and on the presence of a suitable gadget chain. No public exploit code was identified at time of analysis, and the CVE is not confirmed as actively exploited (CISA KEV).
PHP object injection in the Polylang WordPress translation plugin through version 3.8.9 lets an authenticated high-privileged user (CVSS PR:H, typically a WordPress administrator) feed untrusted serialized data into a PHP unserialize() call, which can corrupt application state and, if a usable POP gadget chain exists in WordPress core, Polylang, or another installed component, escalate to code execution or file manipulation. There is no public exploit code identified at time of analysis and no indication of active exploitation (not CISA KEV), so practical risk is currently gated by the administrator-equivalent access requirement rather than by exploitability of the deserialization primitive alone.
Heap-based buffer overflow in GStreamer's gst-plugins-base plugin library lets a local attacker who controls the sending side of a GStreamer inter-process IPC pipeline corrupt memory in the receiving process, yielding a CVSS 3.1 base score of 8.4 (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) with high confidentiality, integrity, and availability impact. The victim process maps a crafted video buffer whose GstVideoMeta declares plane strides and offsets larger than the actual backing allocation, causing out-of-bounds reads and writes that can crash the process or potentially permit code execution in its context. Exploitation is strictly local and requires a deployment where GStreamer buffers cross a trust boundary between a less-trusted producer and a more-trusted consumer; no user interaction or authentication to the victim is needed, and no public exploit has been identified at time of analysis.
Insecure deserialization of untrusted data in HPE NonStop Middleware (CWE-502), combined with weak handling of secret keys, allows an attacker who already holds high privileges on the middleware to submit crafted serialized content and achieve high impact to integrity and availability, with the effect capable of crossing into other security scopes (CVSS 7.9, S:C). The attack is network-reachable but sharply constrained: it requires high privileges (PR:H) and high attack complexity (AC:H), meaning the attacker must defeat the secret-key protection or hit a narrow configuration/state rather than walk a default path, and no user interaction is needed (UI:N). The realistic attacker population is therefore insiders or actors who have already compromised privileged NonStop credentials; no public exploit identified at time of analysis.
PHP Object Injection in the Post Export Import with Media WordPress plugin (versions ≤1.17.1) allows authenticated administrators to inject arbitrary PHP objects via deserialization of untrusted input, but the flaw has no impact unless a separate plugin or theme provides a usable POP gadget chain. If such a chain exists, the attacker could delete files, retrieve sensitive data, or execute code. No public exploit code has been identified, and the issue is considered conditional and lower-priority despite the 7.2 CVSS score.
Unauthenticated remote attackers can corrupt the persisted status of batch job instances on IBM WebSphere Application Server - Liberty versions 17.0.0.3 through 26.0.0.10 via a deserialization flaw (CWE-502), rated CVSS 3.1 base 8.2 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L). Real-world exposure is limited because exploitation requires the optional, non-default Java Batch / JSR-352 batch management and persistence capability to be enabled on a network-reachable Liberty server, and the resulting impact is confined to the integrity of persisted batch state rather than full server compromise. No public exploit code has been identified and there is no confirmed active exploitation (no CISA KEV listing) at time of analysis.
Deserialization of untrusted data in Microsoft SQL Server (SQL Server 2019, 2022, and 2025 GDR/CU builds) allows an attacker to achieve remote code execution with high confidentiality, integrity, and availability impact. Exploitation requires the attacker to already hold valid low-privilege authenticated access to the target instance (CVSS PR:L) plus network reachability (AV:N), with no user interaction (UI:N), so credential-less external attackers cannot exploit it directly; realistic risk concentrates on instances reachable by untrusted or lower-trust database users, such as multi-tenant applications, service accounts, or internal users. CISA's SSVC evaluation rates exploitation as none and automatable as no, and no public exploit code has been identified at time of analysis, but the technical impact is rated total. Microsoft has released fixed builds for every affected branch.
Unauthenticated remote code execution in Xorbits Xoscar through 0.11.2 lets any attacker who can reach the actor-pool TCP channel run arbitrary code as the server process, because the receive path hands raw network bytes straight to cloudpickle.loads() before the message type is validated. The CVSS 4.0 vector (AV:N/PR:N/UI:N, 9.3) confirms the bug is remotely reachable and requires no credentials or user interaction, so any deployment exposing an actor pool on a routable interface is exposed at default configuration; impact is worst where the process runs as root, typical of GPU-node deployments. No public exploit code or confirmed active exploitation was identified at time of analysis, and the exposure is bounded by network reachability - installations that bind the actor-pool port to localhost or keep it on an isolated segment are not remotely exploitable.
Denial of service in IBM WebSphere Application Server 8.5 and 9.0, and in IBM WebSphere Application Server - Liberty 17.0.0.3 through 26.0.0.10, allows remote unauthenticated attackers to disrupt availability by sending crafted serialized data to the product's messaging service. The root cause is insecure deserialization (CWE-502) in the messaging component, rated CVSS 3.1 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), so impact is confined to availability - confidentiality and integrity are not affected. Per the assessed vector, no credentials or user interaction are required once the messaging endpoint is reachable, but the vulnerable code path is only exercised where the messaging engine (SIB/JMS) is enabled and accepting input; environments that disable it or restrict it to trusted networks are materially less exposed. There is no public exploit identified at time of analysis, and this CVE is not listed as confirmed actively exploited (CISA KEV).
Local privilege escalation in Microsoft Windows Media Foundation lets an authenticated, low-privileged attacker who already has a foothold on the host run code at higher integrity by supplying specially crafted serialized data that Media Foundation deserializes. Under the assessed vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) no user interaction is needed and the escalation is reliable once local access exists, but the bug cannot be triggered remotely or by an unauthenticated actor, making it strictly a post-compromise escalation step. Microsoft has published a fix through its update guide, and no public exploit code or confirmed active exploitation was identified at time of analysis.
Local privilege escalation in Windows Management Instrumentation (WMI) lets an authenticated attacker with only low-privilege access on a Windows host elevate to SYSTEM or administrator privileges by feeding crafted serialized data into a vulnerable WMI deserialization path. Successful exploitation requires an existing local foothold and valid credentials (CVSS:3.1 AV:L/AC:L/PR:L/UI:N, base 7.8) and requires no user interaction, so it is not remotely reachable and cannot be triggered by an unauthenticated attacker. No public exploit identified at time of analysis and there is no confirmed active exploitation (CISA KEV) for this issue; a vendor patch is available from Microsoft, so risk is concentrated in environments where attackers have already established a low-privilege presence and where patch cycles are slow.
Remote code execution affects Windows desktop applications built on the Microsoft.WindowsDesktop.App.Runtime (WPF) component of .NET, specifically runtimes 8.0.0 through 8.0.31, 9.0.0 through 9.0.20, 10.0.0 through 10.0.12, and 11.0.0-preview.1 through 11.0.0-rc.1, as well as Visual Studio 2022 17.14 and Visual Studio 2026 18.10 installations that carry the vulnerable runtime. An unauthenticated attacker can deliver crafted content that, when a victim interacts with an XPS document whose synthetic hyperlinks are exposed through UI Automation, bypasses the application's restrictive navigation checks and reaches attacker-controlled content, leading to code execution in the context of the running application; the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, 8.8) confirms high confidentiality, integrity, and availability impact but explicitly requires user interaction. Vendor patches are available (runtime fixes 8.0.32, 9.0.21, 10.0.13, and 11.0.0-rc.2), and no public exploit code was identified at time of analysis despite the network-reachable attack path.
Local privilege escalation in Microsoft Exchange Server stems from deserialization of untrusted data (CWE-502) that an attacker with an existing, authenticated foothold on the host can trigger through the vulnerable code path. Because the attack vector is local (CVSS AV:L, PR:L, UI:N), this is not remotely reachable on its own - it is realistically a post-compromise escalation step that lets an already-present authorized user raise privileges to the Exchange service context, with high impact to confidentiality, integrity, and availability. No public exploit code has been identified at time of analysis and there is no CISA KEV confirmation of active exploitation; vendor patches are available for Exchange Server 2019 CU14, 2016 CU23, and Subscription Edition.
Remote code execution in Microsoft SharePoint Server Subscription Edition (builds below 16.0.20326.20190) lets an authenticated, low-privileged user of a SharePoint deployment send a malicious serialized payload over the network and obtain code execution with high confidentiality and integrity impact, requiring no user interaction from the victim. The issue is a CWE-502 deserialization-of-untrusted-data flaw rated CVSS 3.1 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), and no public exploit has been identified at time of analysis; the decisive exposure factor is the PR:L authentication prerequisite, so practical risk concentrates in deployments where low-privilege, guest, or self-service accounts are broadly provisioned or can be obtained through credential compromise.
Unauthenticated remote attackers can crash Node.js servers running Qwik server-side rendering by sending a crafted resource value that triggers an unhandled promise rejection, affecting @builder.io/qwik before 1.20.0 and @qwik.dev/core before 2.0.0-beta.37. This is an availability-only denial-of-service (CWE-248) assessed at CVSS 3.1 base 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), requiring no authentication or user interaction. No public exploit code or CISA KEV status is reported, but a single request can terminate a process under Node.js default unhandled-rejection policy.
Remote code execution in .NET WPF (Microsoft.WindowsDesktop.App.Runtime) allows an unauthenticated attacker to execute code on a victim's Windows system by crafting a malicious XAML/XPS document or serialized payload and convincing the user to open or load it. The vulnerability is a CWE-502 deserialization of untrusted data issue rated CVSS 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H); exploitation requires user interaction and is not automatable (SSVC Automatable=no, Exploitation=none). No public exploit code or active exploitation has been identified at time of analysis, though vendor patches are available for all affected .NET and .NET Framework versions.
Remote code execution in Microsoft's Windows Presentation Foundation (WPF) component of .NET allows an unauthenticated remote attacker to run arbitrary code on a Windows host, but only when a WPF-based application loads or renders attacker-supplied XAML or XPS content and the victim opens or processes that malicious document (CVSS PR:N/UI:R). The vulnerable component is Microsoft.WindowsDesktop.App.Runtime, affecting .NET 8.0 (<8.0.32), 9.0 (<9.0.21), 10.0 (<10.0.13), 11.0 (<11.0.0-rc.2), .NET Framework 3.5/4.6.2-4.8.1, Visual Studio 2022 17.14 (<17.14.42) and Visual Studio 2026 18.10 (<18.10.4) on Windows only. Publicly available exploit code exists (a public gist is referenced), though CISA SSVC records Exploitation as none and CISA KEV does not list this CVE; CISA's SSVC decision also rates the issue as not automatable, so mass opportunistic scanning is unlikely and practical risk concentrates on environments whose WPF applications consume untrusted markup. Signals are moderately strong but not uniformly alarming: high technical impact (total via SSVC) is tempered by the required user interaction and the absence of a server-side, zero-click remote path in default configurations.
Authenticated remote code execution in Microsoft SharePoint allows a low-privileged user with network access to trigger deserialization of untrusted input, potentially running code on the server. The vulnerability requires a valid SharePoint account (PR:L), needs no user interaction (UI:N), and has low attack complexity (AC:L), but assessed impacts are limited to low confidentiality, integrity, and availability (CVSS 7.4, S:C). No public exploit or active exploitation is indicated in the provided intelligence, and this is a credible but moderate-priority vulnerability, with risk concentrated in environments where SharePoint accounts are broadly provisioned or the service is internet-exposed to authenticated users.
Deserialization of untrusted data in Microsoft Dynamics Business Central (CVE-2026-100214, CVSS 8.8) allows an authenticated attacker with low privileges to execute arbitrary code over the network - the CVSS vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H indicates no user interaction, low attack complexity, and high confidentiality, integrity, and availability impact within the vulnerable component. Exploitation is gated by a valid Business Central account (PR:L), so this is not unauthenticated remote code execution, but once a foothold account exists and the deserialization endpoint is network-reachable, exploitation is straightforward. No public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited (no CISA KEV entry), making this a credible mid-to-high priority issue rather than an emergency; organizations should confirm the specific affected builds and patched versions against the MSRC advisory.
Unsafe deserialization in NVIDIA Megatron-LM's checkpoint-loading routine allows an attacker to execute arbitrary code, escalate privileges, disclose information, and tamper with data by convincing a user to load a maliciously crafted checkpoint or model file into the framework. The flaw is rated CVSS 7.8 (High) and is reachable only when a victim actually opens an attacker-supplied checkpoint, so organizations that load checkpoints exclusively from trusted internal sources are not realistically exposed; the vulnerable path is local (AV:L) and depends on user interaction per our assessment, with no network service or authentication bypass involved. No public exploit code has been identified at time of analysis and the vulnerability is not in CISA KEV, though the availability of proof-of-concept tooling for pickle-based deserialization attacks in ML frameworks makes this class of issue practically exploitable once a crafted checkpoint is delivered.
Deserialization of untrusted data in the NVIDIA Megatron-LM checkpoint-loading path allows code execution, privilege escalation, information disclosure, and data tampering when a user is convinced to load a maliciously crafted checkpoint file. NVIDIA PSIRT scores this CVSS 7.8 (High) and both the vendor and the independent assessment agree on full confidentiality, integrity, and availability impact; the assessments differ on prerequisites, with the vendor vector indicating low privileges and no user interaction (PR:L/UI:N) while the independent assessment models it as no privileges with required victim interaction (PR:N/UI:R). No public exploit code or CISA KEV entry was identified at time of analysis, and only environments that actually load untrusted checkpoints are exposed; code runs with the privileges of the loading user or process, not inherently as root.
Insecure deserialization in Project MONAI's nnUNetV2Runner (versions 1.2.0 up to but not including 1.6.1) lets an attacker who can write to a nnU-Net results directory tamper with inference_information.json and redirect the postprocessing_file field to a malicious Python pickle anywhere on the filesystem, which is then unpickled when predict_ensemble_postprocessing runs, giving arbitrary code execution in the MONAI process. Exploitation is local and requires pre-existing low-privilege filesystem write access plus a legitimate operator subsequently invoking the runner (passive user interaction), so it is a shared-host/multi-tenant concern rather than an internet-facing remote threat; no public exploit code has been identified at time of analysis and the issue is not in CISA KEV. The path-confinement fix and a pickle opt-in gate (MONAI_ALLOW_PICKLE) are available from the vendor as of MONAI 1.6.1, with an associated upstream commit.
Remote code execution in Project MONAI 0.4.0 through 1.6.0 requires an on-path attacker to tamper with SENet pretrained weights fetched over plaintext HTTP, causing construction of SEResNet50 or another SENet model with pretrained=True to unpickle a crafted .pth file because load_state_dict_from_url is used without weights_only=True. The issue is unauthenticated but requires user interaction and a man-in-the-middle position; no public exploit identified at time of analysis. The CVE record rates it CVSS 7.7, though the assessed precondition set makes real-world urgency conditional rather than broadly exploitable.
Configuration-gate bypass in Crawl4AI 0.9.0 through 0.9.3 lets an authenticated but non-admin API client submit a laundered LLMConfig object through the server's configuration endpoint and read back environment-resolved secrets, including SECRET_KEY and provider API keys, which can then be used to forge admin JWTs. Exploitation requires Crawl4AI to be running in server/API mode with the /config/dump endpoint reachable and the attacker to already hold a provisioned non-admin API token (CVSS 4.0 base 8.6, vector PR:L), so pure library or embedded deployments are not affected; impact is highest where SECRET_KEY and provider keys are present in the server environment. Independent assessment flags this as a credible high-priority issue for hosted Crawl4AI deployments, with no public exploit identified at time of analysis and no CISA KEV listing.
Unauthenticated remote code execution is achievable in Square Squash (all versions through commit e73f280) through a two-stage YAML deserialization path in the symbolication API. An attacker first stores crafted YAML under a chosen symbolication UUID using the unauthenticated POST /api/1.0/symbolication endpoint; the payload only detonates when occurrences referencing that UUID are later processed by the symbolication worker, at which point the stored value is passed to YAML.load with SafeYAML running in unsafe mode, permitting arbitrary Ruby object instantiation and code execution. Publicly available exploit code exists, and no CISA KEV listing confirms active exploitation; exploitation is deferred rather than immediate, which is why the assessed complexity is high (AC:H) despite requiring no authentication or user interaction.
Unsafe deserialization in the UYAP Document Editor before version 5.4.20 allows an attacker to inject objects into the application through a crafted document, resulting in code execution with the privileges of the editor process (CVSS 3.1 base 8.8, AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, CWE-502). Exploitation is unauthenticated and network-reachable with low complexity, but requires the victim to open or process an attacker-supplied malicious document (UI:R), which is the principal limiting factor; no public exploit has been identified at time of analysis, and the product is deployed specifically within the Turkish judicial (UYAP) user base, narrowing the realistic target set. Successful exploitation yields high confidentiality, integrity, and availability impact within the affected user's scope.
Remote code execution in ManageIQ (and its downstream Red Hat CloudForms) is possible because the YamlLoadAliases module overrides YAML.safe_load so that in production a Psych::DisallowedClass error silently falls back to YAML.unsafe_load, deserializing arbitrary Ruby objects. An authenticated attacker holding dialog import privileges (CVSS 3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 8.8) can upload a crafted YAML dialog payload containing a disallowed class to trigger an unsafe deserialization path with full confidentiality, integrity, and availability impact. No public exploit code has been identified at time of analysis and there is no CISA KEV listing, but Red Hat CloudForms has reached End of Life and no errata will be issued, so CloudForms operators cannot patch and must depend on restricting the dialog import role.
Unauthenticated PHP Object Injection in the Buzz Stone | Magazine & Viral Blog WordPress theme (vendor themerex) at versions 1.0.2 and earlier lets any remote attacker who can reach an affected request path supply serialized PHP data that the theme passes into an unsafe unserialize() call, yielding a CVSS 3.1 score of 9.8 (AV:N/AC:L/PR:N/UI:N with high confidentiality, integrity, and availability impact). Because the attack is unauthenticated and requires no user interaction, exploitation depends only on the site running this specific niche theme and on a usable POP gadget chain being reachable in the theme, WordPress core, or a co-installed plugin; absent such a gadget, impact is limited to object-injection side effects rather than full remote code execution. No public exploit code has been identified at time of analysis, and the primary limiting factor is narrow deployment - only sites running this particular theme are exposed.
PHP object injection in the Photolia WordPress theme (versions <= 1.0.3) allows unauthenticated remote attackers to trigger deserialization of untrusted data, potentially leading to code execution, file manipulation, or data theft if a usable POP gadget chain exists in the WordPress environment. Although rated CVSS 9.8, the practical risk is tempered by the requirement for a reachable gadget chain in core or co-installed components, and no public exploit has been identified at time of analysis. Site owners should treat this as high severity but prioritize based on exposure.
Unauthenticated PHP object injection in the Qwery WordPress theme (versions 3.6.1 and earlier) allows any remote attacker who can reach an affected site to pass crafted serialized data into a PHP deserialization sink, with no authentication or user interaction required (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, rated 9.8). Because the flaw is CWE-502, real-world impact depends on whether an exploitable PHP gadget chain exists in WordPress core, the theme, or any installed plugin; if such a chain is reachable, the issue can escalate to remote code execution, arbitrary file write, or SQL injection, otherwise impact may be reduced. At the time of analysis there is no confirmed active exploitation (not in CISA KEV) and no public exploit code identified, though the unauthenticated network vector and full C/I/A rating make the theme a high-priority item for any internet-facing WordPress installation running it.
Unauthenticated PHP object injection in the ThemeREX Jacqueline WordPress theme (versions 2.22 and earlier) can let remote attackers achieve full confidentiality, integrity, and availability impact (CVSS 9.8) if a usable POP gadget chain is reachable in the theme or other installed WordPress components. Exploitation requires no authentication or user interaction against a site with the theme active, but the practical impact depends on the presence of a viable gadget chain. No public exploit has been identified at time of analysis, and no vendor-released patch was found in the provided data.
Unauthenticated PHP Object Injection in the ThemeREX Alliance WordPress theme (versions 3.11 and earlier) allows remote attackers to pass crafted serialized data into a PHP unserialize() call, which can lead to arbitrary object instantiation and, where a usable POP gadget chain exists, full compromise of the underlying site with high impact to confidentiality, integrity and availability. The vulnerability carries a CVSS 3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), so no authentication or user interaction is required and default installations are reachable over the network; at time of analysis no public exploit code has been identified and the issue is not listed in CISA KEV, though the EPSS-style risk profile of an unauthenticated WordPress theme flaw of this class typically rises quickly once details circulate. Practical impact depends on the presence of a reachable gadget chain in the theme, WordPress core, or other installed plugins; sites without such a chain may see reduced, but still material, exposure because the injection primitive itself is remotely reachable.
Unauthenticated PHP object injection in the Kicker WordPress theme (AxiomThemes), affecting versions 2.2.1 and earlier, lets any remote attacker reach an unsafe PHP deserialization sink without credentials or user interaction - the only prerequisite is that the theme is active on a network-reachable WordPress site. Rated CVSS 9.8 (AV:N/AC:L/PR:N/UI:N, high C/I/A), the practical severity hinges on CWE-502's classic caveat: achieving code execution, file deletion, or data exfiltration requires a usable POP gadget chain in the theme, an installed plugin, or WordPress core, so impact may be materially lower on sites without a suitable chain. No public exploit code has been identified at time of analysis and the vulnerability is not listed in CISA KEV; Patchstack published the advisory and no vendor-released patch has been confirmed in the provided data.
Unauthenticated PHP object injection in the AxiomThemes 'Original' WordPress theme (all versions up to and including 1.9.0) lets a remote attacker reach a code path that passes attacker-controlled input into PHP's unserialize(), exposing affected sites to high impact across confidentiality, integrity, and availability (CVSS 3.1 base 9.8, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). Because the root cause is CWE-502, the practical ceiling of exploitation depends on whether a usable POP gadget chain exists in the theme, WordPress core, or a co-installed plugin - without one, outcomes may be limited to lower-impact effects rather than full code execution. No public exploit code has been identified at time of analysis, there is no CISA KEV entry indicating confirmed active exploitation, and no EPSS score was supplied with the source data, so this should be treated as a severe latent exposure rather than a confirmed campaign.
Unauthenticated PHP Object Injection in the Anesta WordPress theme (versions up to and including 1.5.3) lets a remote attacker supply a crafted serialized payload that is passed to an unsafe unserialize() call in the theme's code. Because exploitation needs no credentials and no user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 9.8), the realistic impact hinges on whether the site exposes a usable POP gadget chain in the theme, WordPress core, or another active plugin - if such a chain exists, the injected object can trigger file operations, SQL, or code execution with full confidentiality, integrity, and availability impact. No public exploit code has been identified at time of analysis, the issue is not listed in CISA KEV, and no EPSS score was included in the available intelligence; the vulnerable endpoint/parameter is not named in the supplied data and should be confirmed from the Patchstack advisory.
Unauthenticated PHP object injection in the FC United WordPress theme (Axiom Themes, versions up to and including 1.1.1) allows remote attackers to pass crafted serialized input that the theme unserializes without validation, potentially leading to code execution, file manipulation, or database compromise depending on the gadget chains available on the host site. The 9.8 CVSS score reflects a fully remote, unauthenticated attack path with no user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), but there is no public exploit identified at time of analysis and no CISA KEV listing; all severity signals are theoretical rather than empirical. Real-world impact is further bounded by CWE-502's dependency on a reachable POP gadget chain in the theme, WordPress core, or an installed plugin, and by the theme's limited deployment footprint.
Unauthenticated PHP object injection in the ThemeREX ShiftCV WordPress theme, affecting versions up to and including 3.0.14, lets remote attackers feed crafted serialized input into an unsafe deserialization sink, which can escalate to remote code execution when a usable POP gadget chain is reachable in the theme, WordPress core, or an installed plugin. The flaw carries a 9.8 Critical rating (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), meaning no authentication and no user interaction are required and successful exploitation can fully compromise confidentiality, integrity and availability. There is no public exploit identified at time of analysis and no CISA KEV confirmation, so the practical limiting factor is the availability of a reachable gadget chain rather than the injection primitive itself; no EPSS score was supplied in the available intelligence.
Unauthenticated PHP object injection in the WordPress theme Windsor (ThemeREX) through version 2.10 lets remote attackers feed crafted serialized data into an unserialize() call reachable without authentication or user interaction, scoring a maximum base 9.8 under CVSS 3.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). Reported by Patchstack and tracked as CWE-502, the flaw's realized impact depends on whether a usable PHP gadget chain exists across the theme, WordPress core, and installed plugins - in an unpatched site with a suitable gadget, this can escalate to code execution, arbitrary file or data manipulation, whereas without one the injection may be largely inert. At time of analysis there is no public exploit code identified and no CISA KEV listing, so exploitation is not confirmed in the wild; no vendor-released fix version appears in the available advisory data. Given the unauthenticated, network-reachable profile and the prevalence of gadget-rich plugin stacks, this should be treated as high priority for any site running the theme.
Unauthenticated PHP object injection in the ThemeRex Education Center WordPress theme (versions up to and including 3.6.12) lets remote attackers feed serialized data into an unserialize() sink with no authentication and no user interaction, scored CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). Actual damage depends on whether a usable POP gadget chain exists in the theme, WordPress core, or co-installed plugins, because that determines whether object injection escalates to code execution or full confidentiality, integrity, and availability loss. No public exploit code and no CISA KEV listing were identified at time of analysis, and real-world exposure is constrained by the narrow installed base of this specific commercial theme.
Unauthenticated PHP object injection in the Ancorathemes Drone Media WordPress theme, affecting all versions through 2.2.0, lets a remote attacker supply a crafted serialized PHP object to a theme-reachable sink without authentication, no user interaction, and low attack complexity, consistent with the assessed CVSS:3.1/AV:N/AC:L/PR:N/UI:N base vector scored 9.8. Because successful exploitation depends on a usable property-oriented programming (POP) gadget chain being present in the theme, WordPress core, or an installed plugin, the maximum C:H/I:H/A:H impact - typically code execution, file manipulation, or full site takeover - is only realized when such a chain exists; otherwise the realized impact may be lower. At time of analysis there was no public exploit code identified and no evidence of confirmed active exploitation (not listed in CISA KEV), though the combination of an unauthenticated, network-reachable, low-complexity injection sink makes this a high-priority target for attackers once a chain is publicized. Reported by Patchstack against the CPE cpe:2.3:a:ancorathemes:drone_media.
PHP object injection in WooCommerce Multilingual & Multicurrency 5.5.8 and earlier allows an authenticated user with the shop manager role (or higher) to submit crafted serialized input to a plugin endpoint, potentially leading to high confidentiality, integrity, and availability impact if a usable POP gadget chain is present in the loaded code. The vulnerability carries a CVSS 3.1 base score of 7.2 (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) and requires no user interaction beyond the attacker's own authenticated request, but it is not accessible to anonymous visitors or ordinary customers. No public exploit identified at time of analysis.
Unauthenticated PHP object injection in the ThemeRex 'Asia Garden' WordPress theme (versions 1.3.1 and earlier) allows remote attackers to pass crafted serialized data into PHP's unserialize() and instantiate arbitrary objects on the target site. Per the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, 9.8 Critical), exploitation requires no authentication or user interaction against an affected installation and could yield full confidentiality, integrity, and availability impact - typically arbitrary code execution, file manipulation, or SQL injection when a usable POP gadget chain exists in the theme, WordPress core, or an active plugin. No public exploit code has been identified at time of analysis, and the flaw is not confirmed as actively exploited (CISA KEV); no EPSS score was supplied. Practical exploitability hinges on the presence of a viable gadget chain, without which impact may drop to denial of service or be difficult to weaponize, and the exact vulnerable parameter/endpoint is not detailed in the available data.
Unauthenticated PHP object injection in the WordPress theme N7 | Golf Club Sports & Events (versions 2.21 and earlier, vendor ThemeREX) lets a remote attacker supply a crafted serialized PHP object to a theme endpoint without any authentication or user interaction, yielding a CVSS 3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N, C:H/I:H/A:H). Because no public exploit code and no CISA KEV entry were identified at time of analysis, real-world impact hinges on whether a usable POP gadget chain exists in the theme, WordPress core, or a co-installed plugin; where such a chain is reachable, the deserialization flaw can escalate to full remote code execution. Exposure is limited to sites that have this specific niche golf/sports theme installed and active, but for those sites the worst-case profile is complete compromise by an unauthenticated attacker.
Unauthenticated PHP object injection in the ThemeRex Invetex WordPress theme affects versions 2.18 and earlier, allowing remote attackers to supply crafted serialized input to a theme endpoint that performs unsafe deserialization. Successful exploitation can lead to full compromise of the confidentiality, integrity, and availability of the affected site, but the practical ceiling depends on whether a usable PHP POP gadget chain exists in the theme, an active plugin, or WordPress core. No public exploit code or confirmed active exploitation was identified at time of analysis, and the CVSS score should be weighed against the assessed AC:H rather than the reported AC:L.
Unauthenticated PHP object injection in the ThemeRex 'Law Office' WordPress theme at version 3.20 and earlier lets remote attackers with no credentials and no user interaction pass attacker-controlled serialized data into an unsafe unserialize() path, which the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 9.8) scores as complete loss of confidentiality, integrity and availability. Practical impact depends heavily on whether a usable POP gadget chain exists in the theme, an installed plugin, or WordPress core; without a reachable gadget the result may be far below the theoretical 9.8 headline score. No CISA KEV entry, EPSS score, or public exploit code is present in the available intelligence, so this is assessed as no public exploit identified at time of analysis, and exposure is limited to sites running this commercial legal-industry theme.
Unauthenticated PHP object injection in the ThemeRex WineShop WordPress theme (all versions up to and including 3.20) lets remote attackers push attacker-controlled serialized data into a PHP unserialize() operation, enabling instantiation of arbitrary PHP objects and - where a usable gadget chain exists in the theme, co-installed plugins, or the runtime - remote code execution, arbitrary file read/write, or SQL injection. The CVSS 3.1 base score is 9.8 (AV:N/AC:L/PR:N/UI:N), meaning exploitation against a default installation requires no authentication and no user interaction, per the published PR:N/UI:N vector. At time of analysis there is no public exploit code identified and the theme is not listed in CISA KEV; practical exposure is limited to sites actually running this niche wine-shop theme and by whether an exploitable POP gadget chain is reachable.
Unauthenticated PHP object injection in the ThemeRex Equadio WordPress theme (versions up to and including 1.1.4) allows remote attackers to supply crafted serialized input to vulnerable deserialization entry points, potentially leading to remote code execution, file deletion, or other high-impact outcomes depending on available gadget chains. The flaw carries a CVSS 3.1 base score of 9.8, reflecting network exploitability with low complexity, no authentication, and no user interaction required. No public exploit code or active exploitation has been identified at time of analysis, though the severity and ease of exploitation make prompt patching critical.
Unauthenticated PHP Object Injection in the ThemeRex 'Juno' WordPress theme affects all versions up to and including 2.25, allowing remote attackers to supply a crafted serialized PHP object that the theme deserializes without validation. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 9.8) rates this as a network-reachable, low-complexity flaw requiring no credentials and no user interaction, with high confidentiality, integrity and availability impact; however, real-world impact depends on whether a usable POP gadget chain exists in the theme or in co-installed plugins, which is not confirmed in the available data. No public exploit code and no confirmed active exploitation were identified at time of analysis (Patchstack is credited as the reporting source), and exploitation is limited to the subset of WordPress sites running this specific commercial theme at an affected version.
Unauthenticated PHP object injection in the BoldThemes Avala WordPress theme at version 1.1.4 and earlier lets remote attackers pass attacker-controlled data into PHP's unserialize() through a publicly reachable code path, with no authentication or user interaction required (CVSS 3.1 base 9.8, vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). Real-world impact - remote code execution, arbitrary file read/write/delete, or SQL injection - depends on the presence of a usable POP/gadget chain in the theme itself, WordPress core, or another installed plugin; without such a chain the injection may be inert, so the 9.8 score represents a worst-case profile rather than a guaranteed outcome. No public exploit code or confirmed active exploitation was identified at time of analysis, and exploitation requires the Avala theme to be installed and active at version 1.1.4 or below.
Unauthenticated PHP object injection in the Kalles WordPress theme (versions up to and including 1.1.7.1) allows a remote attacker to pass crafted serialized data into a PHP unserialize() call, which on a site that loads a usable gadget chain can escalate to full compromise of the WordPress installation - sensitive data theft, arbitrary content or code modification, and denial of service. The CVSS 3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) describes a network-reachable, low-complexity flaw requiring no credentials and no user interaction, consistent with the CWE-502 classification, and no public exploit has been identified at time of analysis. Real-world impact is bounded by gadget availability in the surrounding WordPress core, plugins, and bundled libraries, so not every installation will reach the full high-confidentiality/integrity/availability outcome.
Unauthenticated PHP object injection in the ThemeRex 'Yacht Rental' WordPress theme affects all versions up to and including 2.6, allowing a remote attacker to pass crafted serialized data into a PHP deserialization path without credentials or user interaction. Per the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N), the theoretical worst case is high confidentiality, integrity, and availability impact with a 9.8 base score. No public exploit code has been identified at time of analysis, and the practical severity depends on whether a usable PHP gadget chain exists within the theme, WordPress core, or co-installed plugins - without such a gadget, real-world impact may be reduced.
Unauthenticated PHP Object Injection in the Wine House WordPress theme (version 3.20 and earlier, distributed by ThemeREX) allows a remote attacker to deliver a crafted serialized payload to an unserialize() call, which the assessed CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) rates at 9.8 Critical with full Confidentiality, Integrity, and Availability impact. Because PR:N and UI:N are confirmed by the vector, no authentication or victim interaction is required - any unauthenticated request to the affected endpoint against a site with the theme installed and active can carry the payload. No public exploit code or confirmed active exploitation was identified at time of analysis, and the practical severity is bounded by whether a usable POP gadget chain exists in the theme, WordPress core, or co-installed plugins; absent such a gadget, impact may degrade to denial of service or be non-exploitable, and the target population is limited to sites running this single commercial theme.
Unauthenticated PHP object injection in the ThemeREX Tipsy WordPress theme through version 1.6 allows remote attackers to supply crafted serialized data that the theme passes to PHP unserialize(), potentially leading to remote code execution, file manipulation, or SQL injection where a usable POP gadget chain exists. Per the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N), the flaw is network-reachable, low-complexity, and requires neither authentication nor user interaction, with full confidentiality, integrity, and availability impact (9.8). No public exploit code has been identified at time of analysis, and the vulnerability is not listed in CISA KEV; exploitation is constrained by the need for an exploitable gadget chain in the theme, WordPress core, or an active plugin.
Unauthenticated PHP object injection in the Stargaze WordPress theme (versions 1.10 and earlier) allows remote attackers to submit a crafted serialized payload that the theme feeds to PHP's unserialize(), which can trigger arbitrary object instantiation and, where a usable gadget chain is present, code execution or full site compromise; the maximum-base CVSS 3.1 score of 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) reflects high confidentiality, integrity, and availability impact. Per that vector no authentication (PR:N) and no user interaction (UI:N) are required, and the CPE record cpe:2.3:a:themerex:stargaze ties the exposure to the ThemeREX Stargaze theme, so only sites with this theme installed and active are in scope. At time of analysis there is no public exploit identified, and the practical ceiling on impact depends on whether a viable POP gadget chain exists in the theme itself, a co-installed plugin, or WordPress core.
Unauthenticated PHP object injection in the ThemeRex Splendour WordPress theme (versions 1.23 and earlier) lets remote attackers pass crafted serialized data into an unsafe deserialization routine, which can lead to remote code execution, arbitrary file manipulation, or full site takeover if a usable gadget chain is reachable. The flaw carries a CVSS 3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) and is classified as CWE-502 Deserialization of Untrusted Data; the vector confirms the entry point is reachable over the network with no authentication and no user interaction. No public exploit code has been identified at time of analysis and the flaw is not confirmed as actively exploited, so real-world impact hinges on the presence of a POP gadget chain in the theme, co-installed plugins, or WordPress core, and on the narrow deployment footprint of this specific commercial theme.
PHP object injection in the Angio WordPress theme (versions 1.1.1 and earlier) allows authenticated attackers with Subscriber-level access to supply malicious serialized data, potentially achieving remote code execution, file manipulation, or other high-impact outcomes if a usable gadget chain exists in the theme, plugins, or WordPress core. Exploitation requires an authenticated Subscriber account (CVSS vector PR:L), which is often obtainable through open user registration, and no public exploit code or active exploitation has been identified at time of analysis. This is a priority-worthy flaw but not an emergency, as practical impact is contingent on the presence of a gadget chain.
Unauthenticated PHP object injection in the Ancora Themes CleanSkin WordPress theme (versions up to and including 1.5.0) allows remote attackers to pass attacker-controlled serialized data into an endpoint that deserializes it, as reflected by a CVSS 3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). The vector confirms the attack is network-reachable, low-complexity, and requires neither authentication nor user interaction against reachable installations, though real-world impact hinges on the presence of a usable POP gadget chain in the theme, WordPress core, or co-installed plugins - without one, the outcome may be limited to the injection itself. No public exploit code was identified at time of analysis and the issue is not confirmed as actively exploited (no CISA KEV listing was provided); the available data contains no documented fixed version.
PHP object injection in the Dynamic User Directory WordPress plugin (versions 2.4 and earlier) allows an attacker holding a low-privileged account to feed attacker-controlled serialized data into an unserialize() call, potentially enabling arbitrary file operations, data disclosure, or remote code execution if a usable POP gadget chain exists within the plugin, WordPress core, or a co-installed plugin. The supplied CVSS 3.1 vector scores 9.8 (AV:N/AC:L/PR:N/UI:N), but our independent assessment lowers the privileges-required metric to Low (PR:L) because the Patchstack 'Subscriber' designation means the attacker must already hold a subscriber-level WordPress account; sites that disable open user registration substantially limit exposure. No public exploit code or confirmed active exploitation was identified at time of analysis.
Unauthenticated PHP object injection in Booster for WooCommerce (WordPress plugin slug woocommerce-jetpack, vendor pluggabl) at version 8.4.0 and earlier allows remote attackers to feed attacker-controlled serialized data into the plugin's deserialization path on any internet-facing WordPress/WooCommerce site, with the assessed CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (9.8 Critical) indicating no credentials, no user interaction, and no non-default configuration are required. Escalation to full remote code execution depends on whether a usable PHP POP gadget chain is reachable in the plugin or other loaded code at the point of unserialization, so the practical worst case is complete site compromise while the minimum case is a deserialization primitive with uncertain downstream effect. There is no public exploit identified at time of analysis and the issue is not listed in CISA KEV; Patchstack is credited as the reporter.
Unauthenticated PHP object injection in Payever WooCommerce Gateway versions up to 4.8.2 allows remote attackers to pass serialized input to an unsafe PHP deserialization path, with a CVSS 3.1 base score of 9.8 reflecting potential full confidentiality, integrity, and availability impact on affected WordPress/WooCommerce sites. The issue is CWE-502 and is network-reachable with low complexity and no privileges or user interaction; no public exploit identified at time of analysis. Practical exploitation may depend on the presence of a usable POP gadget chain, so the real-world outcome can range from limited object injection to full code execution or other high-impact actions.
Unauthenticated PHP Object Injection in the AFFI - Affiliate Marketing for WooCommerce WordPress plugin (all versions through 1.0.10) allows remote attackers to pass crafted serialized data to PHP unserialize(), enabling arbitrary object instantiation that could lead to remote code execution, file manipulation, or data theft if a viable POP gadget chain exists in the plugin, WordPress core, WooCommerce, or other installed extensions. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) confirms no authentication or user interaction is required to reach the vulnerable code path, but the independent assessment notes that real-world severity depends heavily on the presence of a usable gadget chain, making the nominal 9.8 score more nuanced in practice. No public exploit identified at time of analysis, and no CISA KEV listing was provided in the intelligence; the sole reference is the Patchstack vulnerability database entry.
PHP object injection in the bPlugins Super Video Player WordPress plugin affects all versions through 1.8.13, allowing an authenticated high-privilege user to submit untrusted serialized data that the plugin passes to PHP's deserialization routines. Because the CVSS 3.1 vector is AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H (7.2), the weakness is network-reachable and low-complexity but gated behind an administrator-level session in the affected WordPress installation, so anonymous and low-privilege visitors cannot reach the vulnerable path; no public exploit identified at time of analysis, and practical impact depends on the presence of a usable POP gadget chain in WordPress core, the plugin itself, or other installed components.
PHP object injection in the Tainacan WordPress plugin (all versions through 1.3.0) allows an authenticated high-privilege user - per the assessed CVSS vector (PR:H), effectively a WordPress administrator or an equivalent role able to reach the vulnerable input - to pass attacker-controlled serialized data into the plugin's deserialization path and potentially instantiate arbitrary PHP objects. Rated CVSS 3.1 7.2 (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H), the flaw carries high confidentiality and integrity impact but is sharply constrained by the privileged authentication prerequisite and the plugin's niche use as a digital repository/collection management tool for WordPress. No public exploit code or confirmed active exploitation was identified at time of analysis, and object injection would additionally require a usable POP/gadget chain in the loaded codebase to convert into concrete code execution or file manipulation.
Authenticated attackers can exploit a PHP Object Injection flaw (CWE-502) in the WordPress plugin Slider by 10Web (slider-wd) versions up to 1.2.62, potentially achieving remote code execution, file manipulation, or data tampering if a suitable POP gadget chain is present. The vulnerability requires low-privilege authentication (CVSS PR:L) and network access with no user interaction, but its real-world impact is contingent on the availability of a gadget chain in WordPress core or other installed components. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis.
Out-of-bounds read in Apache DataSketches C++ (datasketches-cpp) allows an attacker who controls a serialized VarOpt union image to trigger reads of up to 24 bytes past the end of the supplied buffer, causing a crash (denial of service) and potentially leaking adjacent heap memory into the deserialized union's state. Applications are exposed only if they call var_opt_union::deserialize() on data from untrusted sources; affected releases are 2.0.0-incubating through 5.2.0, and the library is not exploitable on its own. No public exploit code has been identified at time of analysis, EPSS is low at 0.24% (14th percentile), and the issue is not listed in CISA KEV, so the practical priority is moderate rather than urgent. The vendor-released fix is version 5.3.0, which also remediates four other deserialization flaws.
Out-of-bounds read in Apache DataSketches C++ versions 3.1.0 through 5.2.0 is reachable when an application deserializes a compact Theta sketch from an untrusted source, allowing unauthenticated remote attackers to crash the process (denial of service) and potentially disclose adjacent memory contents. The flaw sits in compact_theta_sketch::deserialize() and wrapped_compact_theta_sketch::wrap(), which parse header fields before verifying the input length; in the compressed format a 32-bit integer overflow defeats the length check and two decoding-controlling header fields go unvalidated, and the stream-based deserialization path is affected as well. Apache rates this issue low severity in its 5.3.0 release notes, no public exploit code has been identified at time of analysis, the vulnerability is not in CISA KEV, and EPSS is only 0.20% (9th percentile); exploitation requires the explicit, non-default precondition that the host application accept Theta sketch images from untrusted sources, so the practical priority is lower than the raw 9.1 CVSS might suggest.
Out-of-bounds read and write in the CPC sketch deserialization path of Apache DataSketches C++ (datasketches-cpp) - specifically cpc_sketch::deserialize() called on a byte buffer or a stream - allows a crafted serialized sketch to corrupt heap memory: the decompressor reads past the end of the compressed data because the read position was only checked after decoding finished, and in the hybrid flavor it writes outside an internal heap buffer because decoded row indices were not validated, crashing the process with potential for further exploitation. All releases from 2.0.0-incubating before 5.3.0 are affected, and the CVSS 3.1 base score is 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), indicating remote, unauthenticated impact, but reachability is conditional: only applications that deserialize CPC sketches from untrusted sources are exposed, since the flaw lives in a C++ library whose attack surface depends on the embedding application. Exploitation signals are mixed and should be weighed carefully - EPSS is only 0.19% (8th percentile), there is no CISA KEV entry, and no public exploit identified at time of analysis.
Heap buffer overflow in Apache DataSketches C++ (versions 1.0.0-incubating through 5.2.0) allows an unauthenticated remote attacker who can supply a crafted HLL sketch for deserialization to write up to 988 bytes past a fixed 8-entry internal heap buffer, corrupting memory, crashing the process, and potentially enabling further exploitation. The vulnerable code is a library routine with no network listener of its own, so real-world exposure hinges on whether the consuming application deserializes sketch images from untrusted byte buffers or streams; services that only process trusted or internally generated sketches are not realistically exposed despite the AV:N vector. No public exploit code has been identified at time of analysis, and EPSS is low at 0.21% (11th percentile), while the assessed CVSS 3.1 base of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) reflects the worst case for applications that do accept untrusted sketches, meaning the high score and low observed exploitation signal must be weighed together.
Unauthenticated PHP object injection in the ThemeREX Group 'Booklovers' WordPress theme (all versions through 2.13.0) lets remote attackers feed attacker-controlled serialized data into a PHP unserialize() call, which can corrupt or hijack application logic and, given a reachable gadget chain, escalate to code execution, arbitrary file write, or file deletion. The vulnerability carries a CVSS 3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), meaning no authentication or user interaction is required on a default install, and there is no public exploit identified at time of analysis and no confirmed active exploitation (not in CISA KEV). The practical severity ceiling depends on whether a usable POP gadget chain exists in the theme itself, its bundled plugins, or WordPress core - absent such a chain, exploitation is largely limited to object instantiation with constrained real-world impact.
PHP object injection in the ThemeREX Gutentype WordPress theme (all versions through 2.1.12) allows remote, unauthenticated attackers to inject arbitrary PHP objects through unsafe deserialization of untrusted data, with the potential for full confidentiality, integrity, and availability impact if a usable gadget chain is reachable. The supplied CVSS 3.1 vector scores 9.8 (AV:N/AC:L/PR:N/UI:N/C:H/I:H/A:H), but the independent assessment rates attack complexity as High because practical exploitation depends on the presence of a suitable POP gadget chain in the theme, WordPress core, or an installed plugin - without one, real-world impact is likely lower than the base score implies. No public exploit code has been identified at time of analysis, and the flaw is not confirmed as actively exploited (no CISA KEV listing); exploitation is bounded to sites running the Gutentype theme, unpatched, at version 2.1.12 or earlier.
PHP object injection in the Axiomthemes Balance WordPress theme (versions through 1.12.0) lets uncontrolled serialized data reach a PHP unserialize() call, enabling an attacker to instantiate arbitrary objects within the site's PHP process. Per the assessed vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H), the flaw is remotely reachable without authentication or user interaction, but real-world impact is conditional on the presence of a usable POP gadget chain in the theme, WordPress core, or a co-installed plugin - absent such a gadget the injection can be inert. No public exploit code and no confirmed active exploitation were identified at time of analysis, and no vendor-published fix version is present in the available intelligence; note that the publisher's CVSS vector rates complexity as low (base 9.8) whereas our assessment rates it high, so treat the maximal-impact framing with that caveat.
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.
Unauthenticated access to Apache Kylin's in-house broadcast API combined with polymorphic deserialization of attacker-supplied data exposes Kylin 4.0.0 through 5.0.4 to high-impact compromise of the affected service, assessed as network-reachable without privileges or user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). The vendor classifies the issue as 'moderate' severity but notes that practical risk is concentrated on Kylin instances whose broadcast endpoint is directly reachable from a public network, which Apache describes as 'not common'; typical internal-only deployments are considered largely unimpacted. No CISA KEV entry, EPSS score, or public exploit code was present in the source data, so there is no public exploit identified at time of analysis, and this assessment rests almost entirely on the Apache advisory, which recommends upgrading to Apache Kylin 5.0.5.
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 deserialization in EspoCRM versions prior to 9.3.7 lets an authenticated administrator achieve remote code execution by storing crafted serialized object data in background MassAction or Export parameters that the application later unserializes without any allowed-class restriction. The deserialization sinks are reachable over the network (AV:N) with no user interaction (UI:N), and an attacker with admin credentials can instantiate arbitrary PHP objects and execute code, provided a usable gadget chain is reachable in the deployed codebase or its dependencies. Publicly available exploit code exists, and the vendor released a fix in version 9.3.7; the practical limiting factor is the administrator-privilege prerequisite (PR:H), which tempers real-world urgency even though the flaw is rated 9.1.
PHP object injection in Link Whisper Free (a WordPress plugin) through version 0.9.7 allows unauthenticated remote attackers to pass untrusted data into PHP's unserialize() and instantiate arbitrary objects, per the CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (9.8) supplied with the advisory. Our independent assessment keeps the network-reachable, unauthenticated, no-interaction prerequisites but raises attack complexity to High (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H), because CWE-502 only translates into full confidentiality, integrity, and availability loss when a usable POP gadget chain exists somewhere in the plugin, its bundled libraries, or other code loaded on the target site; absent such a chain the injected object may be inert. No public exploit identified at time of analysis, there is no CISA KEV listing, and no EPSS score was provided, so exposure today is limited to sites running the vulnerable plugin version that also happen to carry a viable gadget chain.
Eclipse Vert.x DB2 Client versions 4.0.0 through 4.5.34, 5.0.0 through 5.0.12, 5.1.0 through 5.1.9, and 5.2.0 can deserialize attacker-controlled DRDA UDT column data, enabling remote code execution if a Java deserialization gadget chain is present on the classpath or denial of service otherwise. The affected component is io.vertx:vertx-db2-client, and exploitation requires an application to connect to a malicious or man-in-the-middle DRDA server that returns a result-set column tagged with FDOCA LID 0x50; legitimate DB2 servers never emit that type, and client-side TLS is disabled by default. The CVSS 4.0 score is 9.2 with PR:N, but practical exploitation requires attacker server-side/MITM position (AC:H) and, for RCE, a classpath gadget chain; no public exploit identified at time of analysis, and the real-world blast radius is narrower than the score alone suggests.
PHP object injection in ILIAS LMS affects installations before 9.24, 10.12, and 11.5, allowing an authenticated user who holds the Test creation or Test import permission to deserialize attacker-controlled objects by importing a crafted Test results archive. By embedding a malicious 'tst_sequence' (sequence) attribute in the archive XML, the attacker reaches an unrestricted unserialize() call and can leverage the bundled Guzzle or Monolog libraries as POP gadget chains to write PHP files and achieve remote code execution on the server. The primary limiting factor is the required authenticated account and import-level permission rather than any anonymous exposure; no public exploit code has been identified at time of analysis and the flaw is not confirmed as actively exploited (no CISA KEV listing).
Unauthenticated PHP object injection in e107 CMS before 2.3.7 lets a remote attacker who can reach install.php execute arbitrary PHP functions with the web server's privileges, resulting in full server compromise (CVSS 3.1 base 9.8, AV:N/AC:L/PR:N/UI:N/C:H/I:H/A:H). The flaw arises because the installer decodes the attacker-controlled previous_steps POST parameter and feeds it to unserialize() without restricting allowed classes, and because install.php remains reachable after a normal installation. No public exploit code was identified at time of analysis and CISA KEV does not list this issue, but the advisory documents a complete, directly usable gadget chain (GuzzleHttp\Psr\7\PumpStream → paths.hash → site_path callable coercion) that makes reliable exploitation realistic for any deployment that left the installer endpoint exposed; sites that deleted or access-restricted install.php after setup are the main mitigating factor.
Denial of service in NASA's F´ (F Prime) framework prior to 4.2.0 allows remote attackers to abort or reset the flight software process by delivering a file-uplink packet whose file-packet type byte falls outside the valid Type enum, driving Fw::FilePacket deserialization into an unvalidated FW_ASSERT (CWE-617). The impact is availability-only, matching the assessed CVSS 3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) with no confidentiality or integrity loss, and the practical limiting factor is reachability: the malicious packet must traverse the Svc::FileUplink file-packet path, which in spaceflight deployments is the ground-to-vehicle uplink. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the vendor has released a fix in F Prime 4.2.0.
Malformed inter-processor hub traffic can abort or reset NASA's F´ (F Prime) flight-software process in versions prior to 4.2.0, because the Svc::GenericHub receive handler treats externally supplied deserialization results as invariants and aborts via FW_ASSERT when they fail. An unauthenticated remote peer on a hub link (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, base 7.5) can send a truncated buffer, a HubType value at or above HUB_TYPE_MAX, or a header-only command-dispatch payload to trigger the fault, producing availability-only impact. The vendor has released 4.2.0 with hardened bounds and type checks; no public exploit code has been identified at time of analysis, and the issue is confined to deployments that genuinely instantiate GenericHub and expose its link to untrusted or spoofable peers.
PHP object injection in the itthinx Affiliates WordPress plugin (all versions through 7.0.1) allows remote, unauthenticated attackers to reach a code path that deserializes attacker-controlled input via unserialize(), which can lead to full object injection against the affected site. The supplied CVSS 3.1 vector scores it 9.8 (AV:N/AC:L/PR:N/UI:N/C:H/I:H/A:H), while our independent assessment applies AC:H because meaningful exploitation depends on the presence of a usable PHP POP gadget chain in the plugin, WordPress core, or another installed plugin/theme; without such a chain the practical effect is usually limited. No public exploit code has been identified at time of analysis, and no CISA KEV listing exists, but sites running Affiliates 7.0.1 or earlier alongside components that expose gadget chains face materially elevated risk.
PHP object injection in the Brainstorm Force SureCart WordPress plugin (all versions through 4.9.3) lets a low-privilege authenticated attacker supply untrusted serialized data that the plugin deserializes, enabling arbitrary object instantiation and, where a usable gadget chain exists in the plugin or its dependencies, escalation to code execution or full site compromise. The CVSS 3.1 base score is 8.8 (High) with vector AV:N/AC:L/PR:L/UI:N and High confidentiality, integrity, and availability impact, and no user interaction is required; exploitation still depends on reaching the specific vulnerable deserialization endpoint and on the presence of a suitable gadget chain. No public exploit code was identified at time of analysis, and the CVE is not confirmed as actively exploited (CISA KEV).
PHP object injection in the Polylang WordPress translation plugin through version 3.8.9 lets an authenticated high-privileged user (CVSS PR:H, typically a WordPress administrator) feed untrusted serialized data into a PHP unserialize() call, which can corrupt application state and, if a usable POP gadget chain exists in WordPress core, Polylang, or another installed component, escalate to code execution or file manipulation. There is no public exploit code identified at time of analysis and no indication of active exploitation (not CISA KEV), so practical risk is currently gated by the administrator-equivalent access requirement rather than by exploitability of the deserialization primitive alone.
Heap-based buffer overflow in GStreamer's gst-plugins-base plugin library lets a local attacker who controls the sending side of a GStreamer inter-process IPC pipeline corrupt memory in the receiving process, yielding a CVSS 3.1 base score of 8.4 (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) with high confidentiality, integrity, and availability impact. The victim process maps a crafted video buffer whose GstVideoMeta declares plane strides and offsets larger than the actual backing allocation, causing out-of-bounds reads and writes that can crash the process or potentially permit code execution in its context. Exploitation is strictly local and requires a deployment where GStreamer buffers cross a trust boundary between a less-trusted producer and a more-trusted consumer; no user interaction or authentication to the victim is needed, and no public exploit has been identified at time of analysis.
Insecure deserialization of untrusted data in HPE NonStop Middleware (CWE-502), combined with weak handling of secret keys, allows an attacker who already holds high privileges on the middleware to submit crafted serialized content and achieve high impact to integrity and availability, with the effect capable of crossing into other security scopes (CVSS 7.9, S:C). The attack is network-reachable but sharply constrained: it requires high privileges (PR:H) and high attack complexity (AC:H), meaning the attacker must defeat the secret-key protection or hit a narrow configuration/state rather than walk a default path, and no user interaction is needed (UI:N). The realistic attacker population is therefore insiders or actors who have already compromised privileged NonStop credentials; no public exploit identified at time of analysis.
PHP Object Injection in the Post Export Import with Media WordPress plugin (versions ≤1.17.1) allows authenticated administrators to inject arbitrary PHP objects via deserialization of untrusted input, but the flaw has no impact unless a separate plugin or theme provides a usable POP gadget chain. If such a chain exists, the attacker could delete files, retrieve sensitive data, or execute code. No public exploit code has been identified, and the issue is considered conditional and lower-priority despite the 7.2 CVSS score.
Unauthenticated remote attackers can corrupt the persisted status of batch job instances on IBM WebSphere Application Server - Liberty versions 17.0.0.3 through 26.0.0.10 via a deserialization flaw (CWE-502), rated CVSS 3.1 base 8.2 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L). Real-world exposure is limited because exploitation requires the optional, non-default Java Batch / JSR-352 batch management and persistence capability to be enabled on a network-reachable Liberty server, and the resulting impact is confined to the integrity of persisted batch state rather than full server compromise. No public exploit code has been identified and there is no confirmed active exploitation (no CISA KEV listing) at time of analysis.
Deserialization of untrusted data in Microsoft SQL Server (SQL Server 2019, 2022, and 2025 GDR/CU builds) allows an attacker to achieve remote code execution with high confidentiality, integrity, and availability impact. Exploitation requires the attacker to already hold valid low-privilege authenticated access to the target instance (CVSS PR:L) plus network reachability (AV:N), with no user interaction (UI:N), so credential-less external attackers cannot exploit it directly; realistic risk concentrates on instances reachable by untrusted or lower-trust database users, such as multi-tenant applications, service accounts, or internal users. CISA's SSVC evaluation rates exploitation as none and automatable as no, and no public exploit code has been identified at time of analysis, but the technical impact is rated total. Microsoft has released fixed builds for every affected branch.
Unauthenticated remote code execution in Xorbits Xoscar through 0.11.2 lets any attacker who can reach the actor-pool TCP channel run arbitrary code as the server process, because the receive path hands raw network bytes straight to cloudpickle.loads() before the message type is validated. The CVSS 4.0 vector (AV:N/PR:N/UI:N, 9.3) confirms the bug is remotely reachable and requires no credentials or user interaction, so any deployment exposing an actor pool on a routable interface is exposed at default configuration; impact is worst where the process runs as root, typical of GPU-node deployments. No public exploit code or confirmed active exploitation was identified at time of analysis, and the exposure is bounded by network reachability - installations that bind the actor-pool port to localhost or keep it on an isolated segment are not remotely exploitable.
Denial of service in IBM WebSphere Application Server 8.5 and 9.0, and in IBM WebSphere Application Server - Liberty 17.0.0.3 through 26.0.0.10, allows remote unauthenticated attackers to disrupt availability by sending crafted serialized data to the product's messaging service. The root cause is insecure deserialization (CWE-502) in the messaging component, rated CVSS 3.1 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), so impact is confined to availability - confidentiality and integrity are not affected. Per the assessed vector, no credentials or user interaction are required once the messaging endpoint is reachable, but the vulnerable code path is only exercised where the messaging engine (SIB/JMS) is enabled and accepting input; environments that disable it or restrict it to trusted networks are materially less exposed. There is no public exploit identified at time of analysis, and this CVE is not listed as confirmed actively exploited (CISA KEV).
Local privilege escalation in Microsoft Windows Media Foundation lets an authenticated, low-privileged attacker who already has a foothold on the host run code at higher integrity by supplying specially crafted serialized data that Media Foundation deserializes. Under the assessed vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) no user interaction is needed and the escalation is reliable once local access exists, but the bug cannot be triggered remotely or by an unauthenticated actor, making it strictly a post-compromise escalation step. Microsoft has published a fix through its update guide, and no public exploit code or confirmed active exploitation was identified at time of analysis.
Local privilege escalation in Windows Management Instrumentation (WMI) lets an authenticated attacker with only low-privilege access on a Windows host elevate to SYSTEM or administrator privileges by feeding crafted serialized data into a vulnerable WMI deserialization path. Successful exploitation requires an existing local foothold and valid credentials (CVSS:3.1 AV:L/AC:L/PR:L/UI:N, base 7.8) and requires no user interaction, so it is not remotely reachable and cannot be triggered by an unauthenticated attacker. No public exploit identified at time of analysis and there is no confirmed active exploitation (CISA KEV) for this issue; a vendor patch is available from Microsoft, so risk is concentrated in environments where attackers have already established a low-privilege presence and where patch cycles are slow.
Remote code execution affects Windows desktop applications built on the Microsoft.WindowsDesktop.App.Runtime (WPF) component of .NET, specifically runtimes 8.0.0 through 8.0.31, 9.0.0 through 9.0.20, 10.0.0 through 10.0.12, and 11.0.0-preview.1 through 11.0.0-rc.1, as well as Visual Studio 2022 17.14 and Visual Studio 2026 18.10 installations that carry the vulnerable runtime. An unauthenticated attacker can deliver crafted content that, when a victim interacts with an XPS document whose synthetic hyperlinks are exposed through UI Automation, bypasses the application's restrictive navigation checks and reaches attacker-controlled content, leading to code execution in the context of the running application; the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, 8.8) confirms high confidentiality, integrity, and availability impact but explicitly requires user interaction. Vendor patches are available (runtime fixes 8.0.32, 9.0.21, 10.0.13, and 11.0.0-rc.2), and no public exploit code was identified at time of analysis despite the network-reachable attack path.
Local privilege escalation in Microsoft Exchange Server stems from deserialization of untrusted data (CWE-502) that an attacker with an existing, authenticated foothold on the host can trigger through the vulnerable code path. Because the attack vector is local (CVSS AV:L, PR:L, UI:N), this is not remotely reachable on its own - it is realistically a post-compromise escalation step that lets an already-present authorized user raise privileges to the Exchange service context, with high impact to confidentiality, integrity, and availability. No public exploit code has been identified at time of analysis and there is no CISA KEV confirmation of active exploitation; vendor patches are available for Exchange Server 2019 CU14, 2016 CU23, and Subscription Edition.
Remote code execution in Microsoft SharePoint Server Subscription Edition (builds below 16.0.20326.20190) lets an authenticated, low-privileged user of a SharePoint deployment send a malicious serialized payload over the network and obtain code execution with high confidentiality and integrity impact, requiring no user interaction from the victim. The issue is a CWE-502 deserialization-of-untrusted-data flaw rated CVSS 3.1 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), and no public exploit has been identified at time of analysis; the decisive exposure factor is the PR:L authentication prerequisite, so practical risk concentrates in deployments where low-privilege, guest, or self-service accounts are broadly provisioned or can be obtained through credential compromise.
Unauthenticated remote attackers can crash Node.js servers running Qwik server-side rendering by sending a crafted resource value that triggers an unhandled promise rejection, affecting @builder.io/qwik before 1.20.0 and @qwik.dev/core before 2.0.0-beta.37. This is an availability-only denial-of-service (CWE-248) assessed at CVSS 3.1 base 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), requiring no authentication or user interaction. No public exploit code or CISA KEV status is reported, but a single request can terminate a process under Node.js default unhandled-rejection policy.
Remote code execution in .NET WPF (Microsoft.WindowsDesktop.App.Runtime) allows an unauthenticated attacker to execute code on a victim's Windows system by crafting a malicious XAML/XPS document or serialized payload and convincing the user to open or load it. The vulnerability is a CWE-502 deserialization of untrusted data issue rated CVSS 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H); exploitation requires user interaction and is not automatable (SSVC Automatable=no, Exploitation=none). No public exploit code or active exploitation has been identified at time of analysis, though vendor patches are available for all affected .NET and .NET Framework versions.
Remote code execution in Microsoft's Windows Presentation Foundation (WPF) component of .NET allows an unauthenticated remote attacker to run arbitrary code on a Windows host, but only when a WPF-based application loads or renders attacker-supplied XAML or XPS content and the victim opens or processes that malicious document (CVSS PR:N/UI:R). The vulnerable component is Microsoft.WindowsDesktop.App.Runtime, affecting .NET 8.0 (<8.0.32), 9.0 (<9.0.21), 10.0 (<10.0.13), 11.0 (<11.0.0-rc.2), .NET Framework 3.5/4.6.2-4.8.1, Visual Studio 2022 17.14 (<17.14.42) and Visual Studio 2026 18.10 (<18.10.4) on Windows only. Publicly available exploit code exists (a public gist is referenced), though CISA SSVC records Exploitation as none and CISA KEV does not list this CVE; CISA's SSVC decision also rates the issue as not automatable, so mass opportunistic scanning is unlikely and practical risk concentrates on environments whose WPF applications consume untrusted markup. Signals are moderately strong but not uniformly alarming: high technical impact (total via SSVC) is tempered by the required user interaction and the absence of a server-side, zero-click remote path in default configurations.
Authenticated remote code execution in Microsoft SharePoint allows a low-privileged user with network access to trigger deserialization of untrusted input, potentially running code on the server. The vulnerability requires a valid SharePoint account (PR:L), needs no user interaction (UI:N), and has low attack complexity (AC:L), but assessed impacts are limited to low confidentiality, integrity, and availability (CVSS 7.4, S:C). No public exploit or active exploitation is indicated in the provided intelligence, and this is a credible but moderate-priority vulnerability, with risk concentrated in environments where SharePoint accounts are broadly provisioned or the service is internet-exposed to authenticated users.
Deserialization of untrusted data in Microsoft Dynamics Business Central (CVE-2026-100214, CVSS 8.8) allows an authenticated attacker with low privileges to execute arbitrary code over the network - the CVSS vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H indicates no user interaction, low attack complexity, and high confidentiality, integrity, and availability impact within the vulnerable component. Exploitation is gated by a valid Business Central account (PR:L), so this is not unauthenticated remote code execution, but once a foothold account exists and the deserialization endpoint is network-reachable, exploitation is straightforward. No public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited (no CISA KEV entry), making this a credible mid-to-high priority issue rather than an emergency; organizations should confirm the specific affected builds and patched versions against the MSRC advisory.
Unsafe deserialization in NVIDIA Megatron-LM's checkpoint-loading routine allows an attacker to execute arbitrary code, escalate privileges, disclose information, and tamper with data by convincing a user to load a maliciously crafted checkpoint or model file into the framework. The flaw is rated CVSS 7.8 (High) and is reachable only when a victim actually opens an attacker-supplied checkpoint, so organizations that load checkpoints exclusively from trusted internal sources are not realistically exposed; the vulnerable path is local (AV:L) and depends on user interaction per our assessment, with no network service or authentication bypass involved. No public exploit code has been identified at time of analysis and the vulnerability is not in CISA KEV, though the availability of proof-of-concept tooling for pickle-based deserialization attacks in ML frameworks makes this class of issue practically exploitable once a crafted checkpoint is delivered.
Deserialization of untrusted data in the NVIDIA Megatron-LM checkpoint-loading path allows code execution, privilege escalation, information disclosure, and data tampering when a user is convinced to load a maliciously crafted checkpoint file. NVIDIA PSIRT scores this CVSS 7.8 (High) and both the vendor and the independent assessment agree on full confidentiality, integrity, and availability impact; the assessments differ on prerequisites, with the vendor vector indicating low privileges and no user interaction (PR:L/UI:N) while the independent assessment models it as no privileges with required victim interaction (PR:N/UI:R). No public exploit code or CISA KEV entry was identified at time of analysis, and only environments that actually load untrusted checkpoints are exposed; code runs with the privileges of the loading user or process, not inherently as root.
Insecure deserialization in Project MONAI's nnUNetV2Runner (versions 1.2.0 up to but not including 1.6.1) lets an attacker who can write to a nnU-Net results directory tamper with inference_information.json and redirect the postprocessing_file field to a malicious Python pickle anywhere on the filesystem, which is then unpickled when predict_ensemble_postprocessing runs, giving arbitrary code execution in the MONAI process. Exploitation is local and requires pre-existing low-privilege filesystem write access plus a legitimate operator subsequently invoking the runner (passive user interaction), so it is a shared-host/multi-tenant concern rather than an internet-facing remote threat; no public exploit code has been identified at time of analysis and the issue is not in CISA KEV. The path-confinement fix and a pickle opt-in gate (MONAI_ALLOW_PICKLE) are available from the vendor as of MONAI 1.6.1, with an associated upstream commit.
Remote code execution in Project MONAI 0.4.0 through 1.6.0 requires an on-path attacker to tamper with SENet pretrained weights fetched over plaintext HTTP, causing construction of SEResNet50 or another SENet model with pretrained=True to unpickle a crafted .pth file because load_state_dict_from_url is used without weights_only=True. The issue is unauthenticated but requires user interaction and a man-in-the-middle position; no public exploit identified at time of analysis. The CVE record rates it CVSS 7.7, though the assessed precondition set makes real-world urgency conditional rather than broadly exploitable.
Configuration-gate bypass in Crawl4AI 0.9.0 through 0.9.3 lets an authenticated but non-admin API client submit a laundered LLMConfig object through the server's configuration endpoint and read back environment-resolved secrets, including SECRET_KEY and provider API keys, which can then be used to forge admin JWTs. Exploitation requires Crawl4AI to be running in server/API mode with the /config/dump endpoint reachable and the attacker to already hold a provisioned non-admin API token (CVSS 4.0 base 8.6, vector PR:L), so pure library or embedded deployments are not affected; impact is highest where SECRET_KEY and provider keys are present in the server environment. Independent assessment flags this as a credible high-priority issue for hosted Crawl4AI deployments, with no public exploit identified at time of analysis and no CISA KEV listing.
Unauthenticated remote code execution is achievable in Square Squash (all versions through commit e73f280) through a two-stage YAML deserialization path in the symbolication API. An attacker first stores crafted YAML under a chosen symbolication UUID using the unauthenticated POST /api/1.0/symbolication endpoint; the payload only detonates when occurrences referencing that UUID are later processed by the symbolication worker, at which point the stored value is passed to YAML.load with SafeYAML running in unsafe mode, permitting arbitrary Ruby object instantiation and code execution. Publicly available exploit code exists, and no CISA KEV listing confirms active exploitation; exploitation is deferred rather than immediate, which is why the assessed complexity is high (AC:H) despite requiring no authentication or user interaction.
Unsafe deserialization in the UYAP Document Editor before version 5.4.20 allows an attacker to inject objects into the application through a crafted document, resulting in code execution with the privileges of the editor process (CVSS 3.1 base 8.8, AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, CWE-502). Exploitation is unauthenticated and network-reachable with low complexity, but requires the victim to open or process an attacker-supplied malicious document (UI:R), which is the principal limiting factor; no public exploit has been identified at time of analysis, and the product is deployed specifically within the Turkish judicial (UYAP) user base, narrowing the realistic target set. Successful exploitation yields high confidentiality, integrity, and availability impact within the affected user's scope.
Remote code execution in ManageIQ (and its downstream Red Hat CloudForms) is possible because the YamlLoadAliases module overrides YAML.safe_load so that in production a Psych::DisallowedClass error silently falls back to YAML.unsafe_load, deserializing arbitrary Ruby objects. An authenticated attacker holding dialog import privileges (CVSS 3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 8.8) can upload a crafted YAML dialog payload containing a disallowed class to trigger an unsafe deserialization path with full confidentiality, integrity, and availability impact. No public exploit code has been identified at time of analysis and there is no CISA KEV listing, but Red Hat CloudForms has reached End of Life and no errata will be issued, so CloudForms operators cannot patch and must depend on restricting the dialog import role.
Unauthenticated PHP Object Injection in the Buzz Stone | Magazine & Viral Blog WordPress theme (vendor themerex) at versions 1.0.2 and earlier lets any remote attacker who can reach an affected request path supply serialized PHP data that the theme passes into an unsafe unserialize() call, yielding a CVSS 3.1 score of 9.8 (AV:N/AC:L/PR:N/UI:N with high confidentiality, integrity, and availability impact). Because the attack is unauthenticated and requires no user interaction, exploitation depends only on the site running this specific niche theme and on a usable POP gadget chain being reachable in the theme, WordPress core, or a co-installed plugin; absent such a gadget, impact is limited to object-injection side effects rather than full remote code execution. No public exploit code has been identified at time of analysis, and the primary limiting factor is narrow deployment - only sites running this particular theme are exposed.
PHP object injection in the Photolia WordPress theme (versions <= 1.0.3) allows unauthenticated remote attackers to trigger deserialization of untrusted data, potentially leading to code execution, file manipulation, or data theft if a usable POP gadget chain exists in the WordPress environment. Although rated CVSS 9.8, the practical risk is tempered by the requirement for a reachable gadget chain in core or co-installed components, and no public exploit has been identified at time of analysis. Site owners should treat this as high severity but prioritize based on exposure.
Unauthenticated PHP object injection in the Qwery WordPress theme (versions 3.6.1 and earlier) allows any remote attacker who can reach an affected site to pass crafted serialized data into a PHP deserialization sink, with no authentication or user interaction required (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, rated 9.8). Because the flaw is CWE-502, real-world impact depends on whether an exploitable PHP gadget chain exists in WordPress core, the theme, or any installed plugin; if such a chain is reachable, the issue can escalate to remote code execution, arbitrary file write, or SQL injection, otherwise impact may be reduced. At the time of analysis there is no confirmed active exploitation (not in CISA KEV) and no public exploit code identified, though the unauthenticated network vector and full C/I/A rating make the theme a high-priority item for any internet-facing WordPress installation running it.
Unauthenticated PHP object injection in the ThemeREX Jacqueline WordPress theme (versions 2.22 and earlier) can let remote attackers achieve full confidentiality, integrity, and availability impact (CVSS 9.8) if a usable POP gadget chain is reachable in the theme or other installed WordPress components. Exploitation requires no authentication or user interaction against a site with the theme active, but the practical impact depends on the presence of a viable gadget chain. No public exploit has been identified at time of analysis, and no vendor-released patch was found in the provided data.
Unauthenticated PHP Object Injection in the ThemeREX Alliance WordPress theme (versions 3.11 and earlier) allows remote attackers to pass crafted serialized data into a PHP unserialize() call, which can lead to arbitrary object instantiation and, where a usable POP gadget chain exists, full compromise of the underlying site with high impact to confidentiality, integrity and availability. The vulnerability carries a CVSS 3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), so no authentication or user interaction is required and default installations are reachable over the network; at time of analysis no public exploit code has been identified and the issue is not listed in CISA KEV, though the EPSS-style risk profile of an unauthenticated WordPress theme flaw of this class typically rises quickly once details circulate. Practical impact depends on the presence of a reachable gadget chain in the theme, WordPress core, or other installed plugins; sites without such a chain may see reduced, but still material, exposure because the injection primitive itself is remotely reachable.
Unauthenticated PHP object injection in the Kicker WordPress theme (AxiomThemes), affecting versions 2.2.1 and earlier, lets any remote attacker reach an unsafe PHP deserialization sink without credentials or user interaction - the only prerequisite is that the theme is active on a network-reachable WordPress site. Rated CVSS 9.8 (AV:N/AC:L/PR:N/UI:N, high C/I/A), the practical severity hinges on CWE-502's classic caveat: achieving code execution, file deletion, or data exfiltration requires a usable POP gadget chain in the theme, an installed plugin, or WordPress core, so impact may be materially lower on sites without a suitable chain. No public exploit code has been identified at time of analysis and the vulnerability is not listed in CISA KEV; Patchstack published the advisory and no vendor-released patch has been confirmed in the provided data.
Unauthenticated PHP object injection in the AxiomThemes 'Original' WordPress theme (all versions up to and including 1.9.0) lets a remote attacker reach a code path that passes attacker-controlled input into PHP's unserialize(), exposing affected sites to high impact across confidentiality, integrity, and availability (CVSS 3.1 base 9.8, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). Because the root cause is CWE-502, the practical ceiling of exploitation depends on whether a usable POP gadget chain exists in the theme, WordPress core, or a co-installed plugin - without one, outcomes may be limited to lower-impact effects rather than full code execution. No public exploit code has been identified at time of analysis, there is no CISA KEV entry indicating confirmed active exploitation, and no EPSS score was supplied with the source data, so this should be treated as a severe latent exposure rather than a confirmed campaign.
Unauthenticated PHP Object Injection in the Anesta WordPress theme (versions up to and including 1.5.3) lets a remote attacker supply a crafted serialized payload that is passed to an unsafe unserialize() call in the theme's code. Because exploitation needs no credentials and no user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 9.8), the realistic impact hinges on whether the site exposes a usable POP gadget chain in the theme, WordPress core, or another active plugin - if such a chain exists, the injected object can trigger file operations, SQL, or code execution with full confidentiality, integrity, and availability impact. No public exploit code has been identified at time of analysis, the issue is not listed in CISA KEV, and no EPSS score was included in the available intelligence; the vulnerable endpoint/parameter is not named in the supplied data and should be confirmed from the Patchstack advisory.
Unauthenticated PHP object injection in the FC United WordPress theme (Axiom Themes, versions up to and including 1.1.1) allows remote attackers to pass crafted serialized input that the theme unserializes without validation, potentially leading to code execution, file manipulation, or database compromise depending on the gadget chains available on the host site. The 9.8 CVSS score reflects a fully remote, unauthenticated attack path with no user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), but there is no public exploit identified at time of analysis and no CISA KEV listing; all severity signals are theoretical rather than empirical. Real-world impact is further bounded by CWE-502's dependency on a reachable POP gadget chain in the theme, WordPress core, or an installed plugin, and by the theme's limited deployment footprint.
Unauthenticated PHP object injection in the ThemeREX ShiftCV WordPress theme, affecting versions up to and including 3.0.14, lets remote attackers feed crafted serialized input into an unsafe deserialization sink, which can escalate to remote code execution when a usable POP gadget chain is reachable in the theme, WordPress core, or an installed plugin. The flaw carries a 9.8 Critical rating (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), meaning no authentication and no user interaction are required and successful exploitation can fully compromise confidentiality, integrity and availability. There is no public exploit identified at time of analysis and no CISA KEV confirmation, so the practical limiting factor is the availability of a reachable gadget chain rather than the injection primitive itself; no EPSS score was supplied in the available intelligence.
Unauthenticated PHP object injection in the WordPress theme Windsor (ThemeREX) through version 2.10 lets remote attackers feed crafted serialized data into an unserialize() call reachable without authentication or user interaction, scoring a maximum base 9.8 under CVSS 3.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). Reported by Patchstack and tracked as CWE-502, the flaw's realized impact depends on whether a usable PHP gadget chain exists across the theme, WordPress core, and installed plugins - in an unpatched site with a suitable gadget, this can escalate to code execution, arbitrary file or data manipulation, whereas without one the injection may be largely inert. At time of analysis there is no public exploit code identified and no CISA KEV listing, so exploitation is not confirmed in the wild; no vendor-released fix version appears in the available advisory data. Given the unauthenticated, network-reachable profile and the prevalence of gadget-rich plugin stacks, this should be treated as high priority for any site running the theme.
Unauthenticated PHP object injection in the ThemeRex Education Center WordPress theme (versions up to and including 3.6.12) lets remote attackers feed serialized data into an unserialize() sink with no authentication and no user interaction, scored CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). Actual damage depends on whether a usable POP gadget chain exists in the theme, WordPress core, or co-installed plugins, because that determines whether object injection escalates to code execution or full confidentiality, integrity, and availability loss. No public exploit code and no CISA KEV listing were identified at time of analysis, and real-world exposure is constrained by the narrow installed base of this specific commercial theme.
Unauthenticated PHP object injection in the Ancorathemes Drone Media WordPress theme, affecting all versions through 2.2.0, lets a remote attacker supply a crafted serialized PHP object to a theme-reachable sink without authentication, no user interaction, and low attack complexity, consistent with the assessed CVSS:3.1/AV:N/AC:L/PR:N/UI:N base vector scored 9.8. Because successful exploitation depends on a usable property-oriented programming (POP) gadget chain being present in the theme, WordPress core, or an installed plugin, the maximum C:H/I:H/A:H impact - typically code execution, file manipulation, or full site takeover - is only realized when such a chain exists; otherwise the realized impact may be lower. At time of analysis there was no public exploit code identified and no evidence of confirmed active exploitation (not listed in CISA KEV), though the combination of an unauthenticated, network-reachable, low-complexity injection sink makes this a high-priority target for attackers once a chain is publicized. Reported by Patchstack against the CPE cpe:2.3:a:ancorathemes:drone_media.
PHP object injection in WooCommerce Multilingual & Multicurrency 5.5.8 and earlier allows an authenticated user with the shop manager role (or higher) to submit crafted serialized input to a plugin endpoint, potentially leading to high confidentiality, integrity, and availability impact if a usable POP gadget chain is present in the loaded code. The vulnerability carries a CVSS 3.1 base score of 7.2 (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) and requires no user interaction beyond the attacker's own authenticated request, but it is not accessible to anonymous visitors or ordinary customers. No public exploit identified at time of analysis.
Unauthenticated PHP object injection in the ThemeRex 'Asia Garden' WordPress theme (versions 1.3.1 and earlier) allows remote attackers to pass crafted serialized data into PHP's unserialize() and instantiate arbitrary objects on the target site. Per the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, 9.8 Critical), exploitation requires no authentication or user interaction against an affected installation and could yield full confidentiality, integrity, and availability impact - typically arbitrary code execution, file manipulation, or SQL injection when a usable POP gadget chain exists in the theme, WordPress core, or an active plugin. No public exploit code has been identified at time of analysis, and the flaw is not confirmed as actively exploited (CISA KEV); no EPSS score was supplied. Practical exploitability hinges on the presence of a viable gadget chain, without which impact may drop to denial of service or be difficult to weaponize, and the exact vulnerable parameter/endpoint is not detailed in the available data.
Unauthenticated PHP object injection in the WordPress theme N7 | Golf Club Sports & Events (versions 2.21 and earlier, vendor ThemeREX) lets a remote attacker supply a crafted serialized PHP object to a theme endpoint without any authentication or user interaction, yielding a CVSS 3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N, C:H/I:H/A:H). Because no public exploit code and no CISA KEV entry were identified at time of analysis, real-world impact hinges on whether a usable POP gadget chain exists in the theme, WordPress core, or a co-installed plugin; where such a chain is reachable, the deserialization flaw can escalate to full remote code execution. Exposure is limited to sites that have this specific niche golf/sports theme installed and active, but for those sites the worst-case profile is complete compromise by an unauthenticated attacker.
Unauthenticated PHP object injection in the ThemeRex Invetex WordPress theme affects versions 2.18 and earlier, allowing remote attackers to supply crafted serialized input to a theme endpoint that performs unsafe deserialization. Successful exploitation can lead to full compromise of the confidentiality, integrity, and availability of the affected site, but the practical ceiling depends on whether a usable PHP POP gadget chain exists in the theme, an active plugin, or WordPress core. No public exploit code or confirmed active exploitation was identified at time of analysis, and the CVSS score should be weighed against the assessed AC:H rather than the reported AC:L.
Unauthenticated PHP object injection in the ThemeRex 'Law Office' WordPress theme at version 3.20 and earlier lets remote attackers with no credentials and no user interaction pass attacker-controlled serialized data into an unsafe unserialize() path, which the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 9.8) scores as complete loss of confidentiality, integrity and availability. Practical impact depends heavily on whether a usable POP gadget chain exists in the theme, an installed plugin, or WordPress core; without a reachable gadget the result may be far below the theoretical 9.8 headline score. No CISA KEV entry, EPSS score, or public exploit code is present in the available intelligence, so this is assessed as no public exploit identified at time of analysis, and exposure is limited to sites running this commercial legal-industry theme.
Unauthenticated PHP object injection in the ThemeRex WineShop WordPress theme (all versions up to and including 3.20) lets remote attackers push attacker-controlled serialized data into a PHP unserialize() operation, enabling instantiation of arbitrary PHP objects and - where a usable gadget chain exists in the theme, co-installed plugins, or the runtime - remote code execution, arbitrary file read/write, or SQL injection. The CVSS 3.1 base score is 9.8 (AV:N/AC:L/PR:N/UI:N), meaning exploitation against a default installation requires no authentication and no user interaction, per the published PR:N/UI:N vector. At time of analysis there is no public exploit code identified and the theme is not listed in CISA KEV; practical exposure is limited to sites actually running this niche wine-shop theme and by whether an exploitable POP gadget chain is reachable.
Unauthenticated PHP object injection in the ThemeRex Equadio WordPress theme (versions up to and including 1.1.4) allows remote attackers to supply crafted serialized input to vulnerable deserialization entry points, potentially leading to remote code execution, file deletion, or other high-impact outcomes depending on available gadget chains. The flaw carries a CVSS 3.1 base score of 9.8, reflecting network exploitability with low complexity, no authentication, and no user interaction required. No public exploit code or active exploitation has been identified at time of analysis, though the severity and ease of exploitation make prompt patching critical.
Unauthenticated PHP Object Injection in the ThemeRex 'Juno' WordPress theme affects all versions up to and including 2.25, allowing remote attackers to supply a crafted serialized PHP object that the theme deserializes without validation. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 9.8) rates this as a network-reachable, low-complexity flaw requiring no credentials and no user interaction, with high confidentiality, integrity and availability impact; however, real-world impact depends on whether a usable POP gadget chain exists in the theme or in co-installed plugins, which is not confirmed in the available data. No public exploit code and no confirmed active exploitation were identified at time of analysis (Patchstack is credited as the reporting source), and exploitation is limited to the subset of WordPress sites running this specific commercial theme at an affected version.
Unauthenticated PHP object injection in the BoldThemes Avala WordPress theme at version 1.1.4 and earlier lets remote attackers pass attacker-controlled data into PHP's unserialize() through a publicly reachable code path, with no authentication or user interaction required (CVSS 3.1 base 9.8, vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). Real-world impact - remote code execution, arbitrary file read/write/delete, or SQL injection - depends on the presence of a usable POP/gadget chain in the theme itself, WordPress core, or another installed plugin; without such a chain the injection may be inert, so the 9.8 score represents a worst-case profile rather than a guaranteed outcome. No public exploit code or confirmed active exploitation was identified at time of analysis, and exploitation requires the Avala theme to be installed and active at version 1.1.4 or below.
Unauthenticated PHP object injection in the Kalles WordPress theme (versions up to and including 1.1.7.1) allows a remote attacker to pass crafted serialized data into a PHP unserialize() call, which on a site that loads a usable gadget chain can escalate to full compromise of the WordPress installation - sensitive data theft, arbitrary content or code modification, and denial of service. The CVSS 3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) describes a network-reachable, low-complexity flaw requiring no credentials and no user interaction, consistent with the CWE-502 classification, and no public exploit has been identified at time of analysis. Real-world impact is bounded by gadget availability in the surrounding WordPress core, plugins, and bundled libraries, so not every installation will reach the full high-confidentiality/integrity/availability outcome.
Unauthenticated PHP object injection in the ThemeRex 'Yacht Rental' WordPress theme affects all versions up to and including 2.6, allowing a remote attacker to pass crafted serialized data into a PHP deserialization path without credentials or user interaction. Per the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N), the theoretical worst case is high confidentiality, integrity, and availability impact with a 9.8 base score. No public exploit code has been identified at time of analysis, and the practical severity depends on whether a usable PHP gadget chain exists within the theme, WordPress core, or co-installed plugins - without such a gadget, real-world impact may be reduced.
Unauthenticated PHP Object Injection in the Wine House WordPress theme (version 3.20 and earlier, distributed by ThemeREX) allows a remote attacker to deliver a crafted serialized payload to an unserialize() call, which the assessed CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) rates at 9.8 Critical with full Confidentiality, Integrity, and Availability impact. Because PR:N and UI:N are confirmed by the vector, no authentication or victim interaction is required - any unauthenticated request to the affected endpoint against a site with the theme installed and active can carry the payload. No public exploit code or confirmed active exploitation was identified at time of analysis, and the practical severity is bounded by whether a usable POP gadget chain exists in the theme, WordPress core, or co-installed plugins; absent such a gadget, impact may degrade to denial of service or be non-exploitable, and the target population is limited to sites running this single commercial theme.
Unauthenticated PHP object injection in the ThemeREX Tipsy WordPress theme through version 1.6 allows remote attackers to supply crafted serialized data that the theme passes to PHP unserialize(), potentially leading to remote code execution, file manipulation, or SQL injection where a usable POP gadget chain exists. Per the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N), the flaw is network-reachable, low-complexity, and requires neither authentication nor user interaction, with full confidentiality, integrity, and availability impact (9.8). No public exploit code has been identified at time of analysis, and the vulnerability is not listed in CISA KEV; exploitation is constrained by the need for an exploitable gadget chain in the theme, WordPress core, or an active plugin.
Unauthenticated PHP object injection in the Stargaze WordPress theme (versions 1.10 and earlier) allows remote attackers to submit a crafted serialized payload that the theme feeds to PHP's unserialize(), which can trigger arbitrary object instantiation and, where a usable gadget chain is present, code execution or full site compromise; the maximum-base CVSS 3.1 score of 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) reflects high confidentiality, integrity, and availability impact. Per that vector no authentication (PR:N) and no user interaction (UI:N) are required, and the CPE record cpe:2.3:a:themerex:stargaze ties the exposure to the ThemeREX Stargaze theme, so only sites with this theme installed and active are in scope. At time of analysis there is no public exploit identified, and the practical ceiling on impact depends on whether a viable POP gadget chain exists in the theme itself, a co-installed plugin, or WordPress core.
Unauthenticated PHP object injection in the ThemeRex Splendour WordPress theme (versions 1.23 and earlier) lets remote attackers pass crafted serialized data into an unsafe deserialization routine, which can lead to remote code execution, arbitrary file manipulation, or full site takeover if a usable gadget chain is reachable. The flaw carries a CVSS 3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) and is classified as CWE-502 Deserialization of Untrusted Data; the vector confirms the entry point is reachable over the network with no authentication and no user interaction. No public exploit code has been identified at time of analysis and the flaw is not confirmed as actively exploited, so real-world impact hinges on the presence of a POP gadget chain in the theme, co-installed plugins, or WordPress core, and on the narrow deployment footprint of this specific commercial theme.
PHP object injection in the Angio WordPress theme (versions 1.1.1 and earlier) allows authenticated attackers with Subscriber-level access to supply malicious serialized data, potentially achieving remote code execution, file manipulation, or other high-impact outcomes if a usable gadget chain exists in the theme, plugins, or WordPress core. Exploitation requires an authenticated Subscriber account (CVSS vector PR:L), which is often obtainable through open user registration, and no public exploit code or active exploitation has been identified at time of analysis. This is a priority-worthy flaw but not an emergency, as practical impact is contingent on the presence of a gadget chain.
Unauthenticated PHP object injection in the Ancora Themes CleanSkin WordPress theme (versions up to and including 1.5.0) allows remote attackers to pass attacker-controlled serialized data into an endpoint that deserializes it, as reflected by a CVSS 3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). The vector confirms the attack is network-reachable, low-complexity, and requires neither authentication nor user interaction against reachable installations, though real-world impact hinges on the presence of a usable POP gadget chain in the theme, WordPress core, or co-installed plugins - without one, the outcome may be limited to the injection itself. No public exploit code was identified at time of analysis and the issue is not confirmed as actively exploited (no CISA KEV listing was provided); the available data contains no documented fixed version.
PHP object injection in the Dynamic User Directory WordPress plugin (versions 2.4 and earlier) allows an attacker holding a low-privileged account to feed attacker-controlled serialized data into an unserialize() call, potentially enabling arbitrary file operations, data disclosure, or remote code execution if a usable POP gadget chain exists within the plugin, WordPress core, or a co-installed plugin. The supplied CVSS 3.1 vector scores 9.8 (AV:N/AC:L/PR:N/UI:N), but our independent assessment lowers the privileges-required metric to Low (PR:L) because the Patchstack 'Subscriber' designation means the attacker must already hold a subscriber-level WordPress account; sites that disable open user registration substantially limit exposure. No public exploit code or confirmed active exploitation was identified at time of analysis.
Unauthenticated PHP object injection in Booster for WooCommerce (WordPress plugin slug woocommerce-jetpack, vendor pluggabl) at version 8.4.0 and earlier allows remote attackers to feed attacker-controlled serialized data into the plugin's deserialization path on any internet-facing WordPress/WooCommerce site, with the assessed CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (9.8 Critical) indicating no credentials, no user interaction, and no non-default configuration are required. Escalation to full remote code execution depends on whether a usable PHP POP gadget chain is reachable in the plugin or other loaded code at the point of unserialization, so the practical worst case is complete site compromise while the minimum case is a deserialization primitive with uncertain downstream effect. There is no public exploit identified at time of analysis and the issue is not listed in CISA KEV; Patchstack is credited as the reporter.
Unauthenticated PHP object injection in Payever WooCommerce Gateway versions up to 4.8.2 allows remote attackers to pass serialized input to an unsafe PHP deserialization path, with a CVSS 3.1 base score of 9.8 reflecting potential full confidentiality, integrity, and availability impact on affected WordPress/WooCommerce sites. The issue is CWE-502 and is network-reachable with low complexity and no privileges or user interaction; no public exploit identified at time of analysis. Practical exploitation may depend on the presence of a usable POP gadget chain, so the real-world outcome can range from limited object injection to full code execution or other high-impact actions.
Unauthenticated PHP Object Injection in the AFFI - Affiliate Marketing for WooCommerce WordPress plugin (all versions through 1.0.10) allows remote attackers to pass crafted serialized data to PHP unserialize(), enabling arbitrary object instantiation that could lead to remote code execution, file manipulation, or data theft if a viable POP gadget chain exists in the plugin, WordPress core, WooCommerce, or other installed extensions. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) confirms no authentication or user interaction is required to reach the vulnerable code path, but the independent assessment notes that real-world severity depends heavily on the presence of a usable gadget chain, making the nominal 9.8 score more nuanced in practice. No public exploit identified at time of analysis, and no CISA KEV listing was provided in the intelligence; the sole reference is the Patchstack vulnerability database entry.
PHP object injection in the bPlugins Super Video Player WordPress plugin affects all versions through 1.8.13, allowing an authenticated high-privilege user to submit untrusted serialized data that the plugin passes to PHP's deserialization routines. Because the CVSS 3.1 vector is AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H (7.2), the weakness is network-reachable and low-complexity but gated behind an administrator-level session in the affected WordPress installation, so anonymous and low-privilege visitors cannot reach the vulnerable path; no public exploit identified at time of analysis, and practical impact depends on the presence of a usable POP gadget chain in WordPress core, the plugin itself, or other installed components.
PHP object injection in the Tainacan WordPress plugin (all versions through 1.3.0) allows an authenticated high-privilege user - per the assessed CVSS vector (PR:H), effectively a WordPress administrator or an equivalent role able to reach the vulnerable input - to pass attacker-controlled serialized data into the plugin's deserialization path and potentially instantiate arbitrary PHP objects. Rated CVSS 3.1 7.2 (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H), the flaw carries high confidentiality and integrity impact but is sharply constrained by the privileged authentication prerequisite and the plugin's niche use as a digital repository/collection management tool for WordPress. No public exploit code or confirmed active exploitation was identified at time of analysis, and object injection would additionally require a usable POP/gadget chain in the loaded codebase to convert into concrete code execution or file manipulation.
Authenticated attackers can exploit a PHP Object Injection flaw (CWE-502) in the WordPress plugin Slider by 10Web (slider-wd) versions up to 1.2.62, potentially achieving remote code execution, file manipulation, or data tampering if a suitable POP gadget chain is present. The vulnerability requires low-privilege authentication (CVSS PR:L) and network access with no user interaction, but its real-world impact is contingent on the availability of a gadget chain in WordPress core or other installed components. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis.
Out-of-bounds read in Apache DataSketches C++ (datasketches-cpp) allows an attacker who controls a serialized VarOpt union image to trigger reads of up to 24 bytes past the end of the supplied buffer, causing a crash (denial of service) and potentially leaking adjacent heap memory into the deserialized union's state. Applications are exposed only if they call var_opt_union::deserialize() on data from untrusted sources; affected releases are 2.0.0-incubating through 5.2.0, and the library is not exploitable on its own. No public exploit code has been identified at time of analysis, EPSS is low at 0.24% (14th percentile), and the issue is not listed in CISA KEV, so the practical priority is moderate rather than urgent. The vendor-released fix is version 5.3.0, which also remediates four other deserialization flaws.
Out-of-bounds read in Apache DataSketches C++ versions 3.1.0 through 5.2.0 is reachable when an application deserializes a compact Theta sketch from an untrusted source, allowing unauthenticated remote attackers to crash the process (denial of service) and potentially disclose adjacent memory contents. The flaw sits in compact_theta_sketch::deserialize() and wrapped_compact_theta_sketch::wrap(), which parse header fields before verifying the input length; in the compressed format a 32-bit integer overflow defeats the length check and two decoding-controlling header fields go unvalidated, and the stream-based deserialization path is affected as well. Apache rates this issue low severity in its 5.3.0 release notes, no public exploit code has been identified at time of analysis, the vulnerability is not in CISA KEV, and EPSS is only 0.20% (9th percentile); exploitation requires the explicit, non-default precondition that the host application accept Theta sketch images from untrusted sources, so the practical priority is lower than the raw 9.1 CVSS might suggest.
Out-of-bounds read and write in the CPC sketch deserialization path of Apache DataSketches C++ (datasketches-cpp) - specifically cpc_sketch::deserialize() called on a byte buffer or a stream - allows a crafted serialized sketch to corrupt heap memory: the decompressor reads past the end of the compressed data because the read position was only checked after decoding finished, and in the hybrid flavor it writes outside an internal heap buffer because decoded row indices were not validated, crashing the process with potential for further exploitation. All releases from 2.0.0-incubating before 5.3.0 are affected, and the CVSS 3.1 base score is 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), indicating remote, unauthenticated impact, but reachability is conditional: only applications that deserialize CPC sketches from untrusted sources are exposed, since the flaw lives in a C++ library whose attack surface depends on the embedding application. Exploitation signals are mixed and should be weighed carefully - EPSS is only 0.19% (8th percentile), there is no CISA KEV entry, and no public exploit identified at time of analysis.
Heap buffer overflow in Apache DataSketches C++ (versions 1.0.0-incubating through 5.2.0) allows an unauthenticated remote attacker who can supply a crafted HLL sketch for deserialization to write up to 988 bytes past a fixed 8-entry internal heap buffer, corrupting memory, crashing the process, and potentially enabling further exploitation. The vulnerable code is a library routine with no network listener of its own, so real-world exposure hinges on whether the consuming application deserializes sketch images from untrusted byte buffers or streams; services that only process trusted or internally generated sketches are not realistically exposed despite the AV:N vector. No public exploit code has been identified at time of analysis, and EPSS is low at 0.21% (11th percentile), while the assessed CVSS 3.1 base of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) reflects the worst case for applications that do accept untrusted sketches, meaning the high score and low observed exploitation signal must be weighed together.
Unauthenticated PHP object injection in the ThemeREX Group 'Booklovers' WordPress theme (all versions through 2.13.0) lets remote attackers feed attacker-controlled serialized data into a PHP unserialize() call, which can corrupt or hijack application logic and, given a reachable gadget chain, escalate to code execution, arbitrary file write, or file deletion. The vulnerability carries a CVSS 3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), meaning no authentication or user interaction is required on a default install, and there is no public exploit identified at time of analysis and no confirmed active exploitation (not in CISA KEV). The practical severity ceiling depends on whether a usable POP gadget chain exists in the theme itself, its bundled plugins, or WordPress core - absent such a chain, exploitation is largely limited to object instantiation with constrained real-world impact.
PHP object injection in the ThemeREX Gutentype WordPress theme (all versions through 2.1.12) allows remote, unauthenticated attackers to inject arbitrary PHP objects through unsafe deserialization of untrusted data, with the potential for full confidentiality, integrity, and availability impact if a usable gadget chain is reachable. The supplied CVSS 3.1 vector scores 9.8 (AV:N/AC:L/PR:N/UI:N/C:H/I:H/A:H), but the independent assessment rates attack complexity as High because practical exploitation depends on the presence of a suitable POP gadget chain in the theme, WordPress core, or an installed plugin - without one, real-world impact is likely lower than the base score implies. No public exploit code has been identified at time of analysis, and the flaw is not confirmed as actively exploited (no CISA KEV listing); exploitation is bounded to sites running the Gutentype theme, unpatched, at version 2.1.12 or earlier.
PHP object injection in the Axiomthemes Balance WordPress theme (versions through 1.12.0) lets uncontrolled serialized data reach a PHP unserialize() call, enabling an attacker to instantiate arbitrary objects within the site's PHP process. Per the assessed vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H), the flaw is remotely reachable without authentication or user interaction, but real-world impact is conditional on the presence of a usable POP gadget chain in the theme, WordPress core, or a co-installed plugin - absent such a gadget the injection can be inert. No public exploit code and no confirmed active exploitation were identified at time of analysis, and no vendor-published fix version is present in the available intelligence; note that the publisher's CVSS vector rates complexity as low (base 9.8) whereas our assessment rates it high, so treat the maximal-impact framing with that caveat.