Export limit exceeded: 418272 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (3871 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-103039 | 2 Gravityforms, Wordpress-extensions | 2 Gravity Forms, Gravity Forms | 2026-10-30 | 9.8 Critical |
| The Gravity Forms plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 3.1.2 via a Post Custom Field whose input type is List. This is due to GFFormsModel::create_post() passing the submitted value to WordPress' unrestricted global maybe_unserialize() rather than the plugin's own hardened GFCommon::maybe_unserialize(), which was added in 3.1.1 and passes allowed_classes => false precisely to prevent object instantiation. Where the field has a content template enabled, the submitted row reaches that call verbatim. This makes it possible for unauthenticated attackers to inject a PHP object into post meta. No PHP Object Injection gadget chain is present in the plugin itself; however, if a gadget chain is present via an additional plugin or theme, it could allow the attacker to perform actions such as remote code execution. Where the custom field is mapped to the protected _wp_page_template meta key, WordPress itself supplies the chain: validate_file() accepts non-scalars, WP_Theme::__toString() then resolves an attacker-controlled path, and on hosts with a readable PEAR install and register_argc_argv enabled this yields remote code execution. | ||||
| CVE-2026-62848 | 1 Metalama | 1 Metalama | 2026-10-30 | 7.3 High |
| Metalama is a Roslyn-based open-source patterns and architecture toolkit for C#. From 2023.0.101-rc until 2025.1.18, 2026.0.25 and 2026.1.19, the Windows Visual Studio integration deserializes local named-pipe messages without restricting which CLR types can be instantiated. The pipe connects `devenv`, the out-of-process Roslyn code-analysis process and the `CodeLens` process, and has the predictable name `Metalama_{role}_{processId}_{hash(PackageVersion)}`. Releases from the first public 2023.0 line through 2026.0.x use Newtonsoft.Json with `TypeNameHandling.All`; the later `SerializationBinder` only remaps assembly names, and `BindToType` resolves arbitrary wire-supplied types without an allow-list. Releases 2026.1.0 through 2026.1.18 use typeless MessagePack with `TypelessObjectResolver` and likewise instantiate arbitrary types. A same-user local process able to write to the pipe can send crafted messages that lead to arbitrary code execution with confidentiality, integrity and availability impacts inside the affected Visual Studio process. Default Windows pipe ACLs limit writers to the same logged-in user, so this does not escalate privileges or cross a security boundary; command-line and MSBuild-only builds do not use the channel. The maintained Metalama + PostSharp extension is affected from 2024.1 through 2026.1.4, while earlier Metalama-free PostSharp versions are unaffected. The retired Metalama and Caravela extensions remain affected and require removal or migration. The framework issue is fixed in versions 2025.1.18, 2026.0.25 and 2026.1.19; the maintained Metalama + PostSharp Visual Studio extension is fixed in version 2026.1.5. The retired Metalama and Caravela extensions require removal or migration. | ||||
| CVE-2026-16760 | 1 Trailofbits | 1 Fickling | 2026-10-30 | 8.8 High |
| In Trail of Bits fickling through 0.1.12, the _process_import() method in fickle.py adds an imported name to the likely_safe_imports set whenever the source module is present in sys.stdlib_module_names and the name is absent from the UNSAFE_IMPORTS denylist, without inspecting what the name resolves to or how it behaves. The OvertlyBadEvals analysis pass in analysis.py then unconditionally skips any call whose function name appears in likely_safe_imports, including calls that would otherwise be flagged as overtly dangerous. As a result, any callable reachable through a non-blocked standard library module inherits module-level trust regardless of its own behavior, and check_safety() returns LIKELY_SAFE with zero findings for pickle payloads that reach code execution or file write through such callables. Demonstrated primitives: dataclasses._create_fn, which passes an attacker-controlled function body to exec() and yields arbitrary code execution on Python 3.7 through 3.12 (the internal _create_fn function was removed in Python 3.13); mailcap.findmatch, which internally calls os.system() on a test command taken from an attacker-controlled caps dictionary, yielding arbitrary code execution on Python versions through 3.12 (the mailcap module was removed in Python 3.13); and readline.add_history() followed by readline.write_history_file(), which writes attacker-controlled content to an arbitrary filesystem path (POSIX platforms, where the readline module is available). fickling.load() chains check_safety() into pickle.loads() as an explicit security gate, so a LIKELY_SAFE verdict causes the payload to be deserialized and executed with the privileges of the victim process. The root cause is the inference of callable safety from module origin; it is independent of, and separately fixable from, the dotted __qualname__ resolution weakness tracked as CVE-2026-118938, which this advisory does not address. As of 2026-10-30 the three demonstrated modules were added to UNSAFE_IMPORTS on the vendor master branch (commit d011709) pending release; released versions through 0.1.12 remain affected, and the module-origin trust root cause persists, as demonstrated by the related CVE-2026-118938 remaining exploitable on that same build. | ||||
| CVE-2026-93327 | 1 Google | 1 Application Integration | 2026-10-30 | N/A |
| A Deserialization of Untrusted Data vulnerability in the SubWorkflow task in Google Cloud Application Integration versions prior to 2026-09-11 on Google Cloud Platform allows an authenticated attacker to execute arbitrary code using a maliciously crafted serialized object. This vulnerability was patched on 11 September 2026, and no customer action is needed. | ||||
| CVE-2026-73186 | 2 Shortpixel, Wordpress-extensions | 2 Enable Media Replace, Enable Media Replace | 2026-10-30 | 8.8 High |
| Subscriber PHP Object Injection in Enable Media Replace <= 4.2.2 versions. | ||||
| CVE-2026-118089 | 2026-10-30 | 7.2 High | ||
| Shop manager PHP Object Injection in Product Feed Manager <= 7.14.1 versions. | ||||
| CVE-2026-118090 | 2026-10-30 | 8.8 High | ||
| Subscriber PHP Object Injection in MasterStudy LMS <= 3.7.55 versions. | ||||
| CVE-2026-62131 | 2026-10-30 | 9.8 Critical | ||
| Unauthenticated PHP Object Injection in Zoho Flow <= 2.14.5 versions. | ||||
| CVE-2026-62016 | 2026-10-30 | 9.8 Critical | ||
| Unauthenticated PHP Object Injection in Gamic <= 1.19 versions. | ||||
| CVE-2026-62015 | 2026-10-30 | 9.8 Critical | ||
| Unauthenticated PHP Object Injection in Gamezone <= 1.1.11 versions. | ||||
| CVE-2026-62014 | 2026-10-30 | 9.8 Critical | ||
| Unauthenticated PHP Object Injection in EmojiNation <= 1.0.12 versions. | ||||
| CVE-2026-62011 | 2026-10-30 | 9.8 Critical | ||
| Unauthenticated PHP Object Injection in Bonbon <= 1.11 versions. | ||||
| CVE-2026-62010 | 2026-10-30 | 9.8 Critical | ||
| Unauthenticated PHP Object Injection in Avventure <= 1.1.12 versions. | ||||
| CVE-2026-62009 | 2026-10-30 | 9.8 Critical | ||
| Unauthenticated PHP Object Injection in Filmax <= 1.1.11 versions. | ||||
| CVE-2026-62005 | 2026-10-30 | 9.8 Critical | ||
| Unauthenticated PHP Object Injection in Muzicon <= 1.15 versions. | ||||
| CVE-2026-62004 | 2026-10-30 | 9.8 Critical | ||
| Unauthenticated PHP Object Injection in Motorix <= 1.11 versions. | ||||
| CVE-2026-62003 | 2026-10-30 | 9.8 Critical | ||
| Unauthenticated PHP Object Injection in Mission <= 1.22 versions. | ||||
| CVE-2026-61998 | 2026-10-30 | 9.8 Critical | ||
| Unauthenticated PHP Object Injection in Le Truffe <= 1.1.7 versions. | ||||
| CVE-2026-61997 | 2026-10-30 | 9.8 Critical | ||
| Unauthenticated PHP Object Injection in Legal Stone <= 1.2.11 versions. | ||||
| CVE-2026-61992 | 2026-10-30 | 9.8 Critical | ||
| Unauthenticated PHP Object Injection in GEO my WordPress <= 4.5.5.3 versions. | ||||