Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

CWE-502 (可信数据的反序列化) — Vulnerability Class 2486

2486 vulnerabilities classified as CWE-502 (可信数据的反序列化). AI Chinese analysis included.

CWE-502 represents a critical security weakness where applications deserialize untrusted data without validating its integrity or structure. Attackers typically exploit this vulnerability by crafting malicious serialized objects that, when processed by the application, trigger unintended code execution or logic flaws. This often leads to remote code execution, denial of service, or privilege escalation, as the deserialization process may instantiate dangerous classes or invoke unsafe methods. To mitigate this risk, developers must strictly avoid deserializing data from untrusted sources. Instead, they should implement robust input validation, use allowlists for permitted data types, or adopt safer serialization formats like JSON that do not inherently support arbitrary object instantiation. Additionally, employing cryptographic signatures to verify data authenticity before deserialization ensures that only trusted, unaltered payloads are processed, effectively neutralizing the threat of malicious object injection.

MITRE CWE Description
The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
Common Consequences (3)
Integrity Modify Application Data, Unexpected State
Attackers can modify unexpected objects or data that was assumed to be safe from modification. Deserialized data or code could be modified without using the provided accessor functions, or unexpected functions could be invoked.
Availability DoS: Resource Consumption (CPU)
If a function is making an assumption on when to terminate, based on a sentry in a string, it could easily never terminate.
Other Varies by Context
The consequences can vary widely, because it depends on which objects or methods are being deserialized, and how they are used. Making an assumption that the code in the deserialized object is valid is dangerous and can enable exploitation. One example is attackers using gadget chains to perform una…
Mitigations (5)
Architecture and Design, Implementation If available, use the signing/sealing features of the programming language to assure that deserialized data has not been tainted. For example, a hash-based message authentication code (HMAC) could be used to ensure that data has not been modified.
Implementation When deserializing data, populate a new object rather than just deserializing. The result is that the data flows through safe input validation and that the functions are safe.
Implementation Explicitly define a final object() to prevent deserialization.
Architecture and Design, Implementation Make fields transient to protect them from deserialization. An attempt to serialize and then deserialize a class containing transient fields will result in NULLs where the transient data should be. This is an excellent way to prevent time, environment-based, or sensitive variables from being carried over and used improperly.
Implementation Avoid having unnecessary types or gadgets (a sequence of instances and method invocations that can self-execute during the deserialization process, often found in libraries) available that can be leveraged for malicious ends. This limits the potential for unintended or unauthorized types and gadgets to be leveraged by the attacker. Add only acceptable classes to an allowlist. Note: new gadgets are…
Examples (2)
This code snippet deserializes an object from a file and uses it as a UI button:
try { File file = new File("object.obj"); ObjectInputStream in = new ObjectInputStream(new FileInputStream(file)); javax.swing.JButton button = (javax.swing.JButton) in.readObject(); in.close(); }
Bad · Java
private final void readObject(ObjectInputStream in) throws java.io.IOException { throw new java.io.IOException("Cannot be deserialized"); }
Good · Java
In Python, the Pickle library handles the serialization and deserialization processes. In this example derived from [REF-467], the code receives and parses data, and afterwards tries to authenticate a user based on validating a token.
try { class ExampleProtocol(protocol.Protocol): def dataReceived(self, data): # Code that would be here would parse the incoming data # After receiving headers, call confirmAuth() to authenticate def confirmAuth(self, headers): try: token = cPickle.loads(base64.b64decode(headers['AuthToken'])) if not check_hmac(token['signature'], token['data'], getSecretKey()): raise AuthFail self.secure_data = token['data'] except: raise AuthFail }
Bad · Python
CVE ID Title CVSS Severity Published
CVE-2026-93933 WordPress Rosalinda theme <= 1.2.4 - PHP Object Injection vulnerability — Rosalinda 9.8 Critical 2026-10-10
CVE-2026-93932 WordPress Smart Casa theme <= 1.0.12 - PHP Object Injection vulnerability — Smart Casa 9.8 Critical 2026-10-10
CVE-2026-93927 WordPress Veto theme <= 1.6.0 - PHP Object Injection vulnerability — Veto 9.8 Critical 2026-10-10
CVE-2026-93930 WordPress Tantra theme <= 2.9.0 - PHP Object Injection vulnerability — Tantra 9.8 Critical 2026-10-10
CVE-2026-93929 WordPress Travesia theme <= 1.1.16 - PHP Object Injection vulnerability — Travesia 9.8 Critical 2026-10-10
CVE-2026-93931 WordPress Smash theme <= 1.12.0 - PHP Object Injection vulnerability — Smash 9.8 Critical 2026-10-10
CVE-2026-106606 WordPress YITH WooCommerce Affiliates plugin <= 3.31.0 - PHP Object Injection vulnerability — YITH WooCommerce Affiliates 7.2 High 2026-10-10
CVE-2026-12626 Online Scheduling and Appointment Booking System <= 28.2 - Authenticated (Custom+) PHP Object Injection via 'value' Parameter — Online Scheduling and Appointment Booking System – Bookly 7.2 High 2026-10-10
CVE-2026-104723 LifterLMS <= 10.2.1 - Authenticated (Custom+) PHP Object Injection via 'custom' Lesson Data — LifterLMS – WP LMS for eLearning, Online Courses, & Quizzes 8.8 High 2026-10-10
CVE-2026-94065 WordPress ColorFolio theme <= 1.3 - PHP Object Injection vulnerability — ColorFolio 8.8 High 2026-10-09
CVE-2026-94064 WordPress Neo | Barber Shop WordPress Theme theme <= 3.5 - PHP Object Injection vulnerability — Neo | Barber Shop WordPress Theme 8.8 High 2026-10-09
CVE-2026-100730 Grid Protection Alliance openPDC and openHistorian Deserialization of Untrusted Data — openPDC 9.8 Critical 2026-10-09
CVE-2026-104392 WordPress Quiz And Survey Master plugin <= 11.2.7 - PHP Object Injection vulnerability — Quiz And Survey Master 8.8 High 2026-10-09
CVE-2026-105872 WordPress Product Configurator for WooCommerce plugin <= 1.7.5 - PHP Object Injection vulnerability — Product Configurator for WooCommerce 7.2 High 2026-10-09
CVE-2026-94568 WordPress Pay with Vipps for WooCommerce plugin <= 6.2.0 - PHP Object Injection vulnerability — Pay with Vipps for WooCommerce 7.2 High 2026-10-09
CVE-2026-88131 Microsoft Dataverse Remote Code Execution Vulnerability — Microsoft Dataverse 9.8 Critical 2026-10-08
CVE-2026-78401 Security vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access — Security Verify Access 9.8 Critical 2026-10-08
CVE-2026-78406 Security vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access — Security Verify Access 9.8 Critical 2026-10-08
CVE-2026-105436 WordPress MainWP Child plugin <= 6.2.1 - Deserialization of untrusted data vulnerability — MainWP Child 8.8 High 2026-10-08
CVE-2026-82627 Uncanny Automator – AI + Automation for WordPress | AI Agent, AI Page Builder, Free AI Usage Included <= 7.6.1.1 - Authenticated (Subscriber+) PHP Object Injection to Arbitrary File Deletion — Uncanny Automator – AI + Automation for WordPress | AI Agent, AI Page Builder, Free AI Usage Included 7.5 High 2026-10-08
CVE-2026-95606 WordPress The Events Calendar plugin <= 6.17.4 - PHP Object Injection vulnerability — The Events Calendar 9.8 Critical 2026-10-07
CVE-2026-95534 WordPress Unlimited Elements For Elementor (Free Widgets, Addons, Templates) plugin <= 2.0.19 - PHP Object Injection vulnerability — Unlimited Elements For Elementor (Free Widgets, Addons, Templates) 8.8 High 2026-10-07
CVE-2026-106558 Backstage: Improper validation of TechDocs MkDocs configuration — backstage 8.8 High 2026-10-07
CVE-2026-105192 LMCache Unauthenticated RCE in multiprocess mode via pickle deserialization — LMCache 9.8 Critical 2026-10-07
CVE-2025-64393 Veeam Backup & Replication 备份查看器任意代码执行漏洞 — Backup and Replication 9.4 Critical 2026-10-07
CVE-2026-107104 Unsafe Deserialization Vulnerability in Manacle Technologies ERP System — Multi-tenant ERP System 9.3 Critical 2026-10-07
CVE-2026-93447 Langflow OSS is affected by multiple vulnerabilities — Langflow OSS 7.5 High 2026-10-07
CVE-2026-65142 NVIDIA Model-Optimizer未信任数据反序列化漏洞 — Model-Optimizer 7.8 High 2026-10-06
CVE-2026-103831 Insecure deserialization in the TrueLayer Magento 2 plugin — TrueLayer Magento 2 Plugin 7.5 High 2026-10-06
CVE-2026-104747 WordPress Haaken theme <= 1.5 - PHP Object Injection vulnerability — Haaken 8.1 High 2026-10-06

Vulnerabilities classified as CWE-502 (可信数据的反序列化) represent 2486 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.