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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

1687 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)
IntegrityModify 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.
AvailabilityDoS: 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.
OtherVaries 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, ImplementationIf 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.
ImplementationWhen 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.
ImplementationExplicitly define a final object() to prevent deserialization.
Architecture and Design, ImplementationMake 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.
ImplementationAvoid 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 IDTitleCVSSSeverityPublished
CVE-2025-3162 InternLM LMDeploy PT File utils.py load_weight_ckpt deserialization — LMDeploy 5.3 Medium2025-04-03
CVE-2025-30889 WordPress Testimonial Slider plugin <= 2.0.13 - PHP Object Injection vulnerability — Testimonial Slider 8.8 High2025-04-03
CVE-2024-39780 Use of unsafe yaml load in dynparam — Robot Operating System (ROS) 7.8 High2025-04-02
CVE-2025-31612 WordPress CBX Poll plugin <= 2.0.4 - PHP Object Injection vulnerability — CBX Poll 9.8 Critical2025-04-01
CVE-2025-30892 WordPress WpTravelly Plugin <= 1.8.7 - PHP Object Injection vulnerability — WpTravelly 8.8 High2025-04-01
CVE-2025-27130 Welcart e-Commerce 代码问题漏洞 — Welcart e-Commerce 9.8 -2025-04-01
CVE-2025-30065 Apache Parquet Java: Arbitrary code execution in the parquet-avro module when reading an Avro schema from a Parquet file metadata — Apache Parquet Java 9.8AICriticalAI2025-04-01
CVE-2025-31084 WordPress Sunshine Photo Cart plugin <= 3.4.10 - PHP Object Injection Vulnerability — Sunshine Photo Cart 9.8 Critical2025-04-01
CVE-2025-31087 WordPress Multiple Shipping And Billing Address For Woocommerce plugin <= 1.5 - PHP Object Injection Vulnerability — Multiple Shipping And Billing Address For Woocommerce 9.8 Critical2025-04-01
CVE-2025-31074 WordPress MDJM Event Management plugin <= 1.7.5.2 - PHP Object Injection vulnerability — Mobile DJ Manager 8.8 High2025-04-01
CVE-2025-31129 jooby-pac4j: deserialization of untrusted data — jooby 8.8 High2025-03-31
CVE-2025-31103 appleple a-blog cms 代码问题漏洞 — a-blog cms (Ver.3.1.x series) 9.8 -2025-03-31
CVE-2025-22526 WordPress PHP/MySQL CPU performance statistics Plugin <= 1.2.1 - PHP Object Injection vulnerability — PHP/MySQL CPU performance statistics 9.8 Critical2025-03-28
CVE-2025-2485 Drag and Drop Multiple File Upload for Contact Form 7 <= 1.3.8.7 - Unauthenticated PHP Object Injection via PHAR to Arbitrary File Deletion — Drag and Drop Multiple File Upload for Contact Form 7 7.5 High2025-03-28
CVE-2025-26873 WordPress Traveler theme <= 3.1.8 - PHP Object Injection vulnerability — Traveler 9.0 Critical2025-03-27
CVE-2025-2855 elunez eladmin upload checkFile deserialization — eladmin 4.7 Medium2025-03-27
CVE-2025-30773 WordPress TranslatePress plugin <= 2.9.6 - PHP Object Injection Vulnerability — TranslatePress 7.2 High2025-03-27
CVE-2025-2332 Export All Posts, Products, Orders, Refunds & Users <= 2.13 - Unauthenticated PHP Object Injection — Export All Posts, Products, Orders, Refunds & Users 9.8 Critical2025-03-27
CVE-2025-1913 Product Import Export for WooCommerce <= 2.5.0 - Authenticated (Admin+) PHP Object Injection via form_data Parameter — Product Import Export for WooCommerce – Import Export Product CSV Suite 7.2 High2025-03-26
CVE-2024-13889 WordPress Importer <= 0.8.3 - Authenticated (Administrator+) PHP Object Injection — WordPress Importer 7.2 High2025-03-26
CVE-2025-2690 yiisoft Yii2 MockClass.php generate deserialization — Yii2 6.3 Medium2025-03-24
CVE-2025-2689 yiisoft Yii2 SortableIterator.php getIterator deserialization — Yii2 6.3 Medium2025-03-24
CVE-2025-2622 aizuda snail-job Workflow-Task Management Module check-node-expression getRuntime deserialization — snail-job 6.3 Medium2025-03-22
CVE-2025-1971 Export and Import Users and Customers <= 2.6.2 - Authenticated (Admin+) PHP Object Injection via form_data Parameter — Export and Import Users and Customers 7.2 High2025-03-22
CVE-2025-0724 ProfileGrid – User Profiles, Groups and Communities <= 5.9.4.5 - Authenticated (Subscriber+) PHP Object Injection — ProfileGrid – User Profiles, Groups and Communities 8.8 High2025-03-22
CVE-2025-29807 Microsoft Dataverse Remote Code Execution Vulnerability — Microsoft Dataverse 8.7 High2025-03-21
CVE-2024-13921 Order Export & Order Import for WooCommerce <= 2.6.0 - Authenticated (Admin+) PHP Object Injection via form_data Parameter — Order Export & Order Import for WooCommerce 7.2 High2025-03-20
CVE-2024-11041 Remote Code Execution in vllm-project/vllm — vllm-project/vllm 9.8 -2025-03-20
CVE-2024-9070 Deserialization Vulnerability in BentoML's Runner Server in bentoml/bentoml — bentoml/bentoml 9.8 -2025-03-20
CVE-2024-12433 Remote Code Execution in infiniflow/ragflow — infiniflow/ragflow 9.8 -2025-03-20

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