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-62086 WordPress Juno theme <= 2.25 - PHP Object Injection vulnerability — Juno 9.8 Critical 2026-10-10
CVE-2026-62076 WordPress Kalles theme <= 1.1.7.1 - PHP Object Injection vulnerability — Kalles 9.8 Critical 2026-10-10
CVE-2026-62077 WordPress Avala theme <= 1.1.4 - PHP Object Injection vulnerability — Avala 9.8 Critical 2026-10-10
CVE-2026-62054 WordPress Yacht Rental theme <= 2.6 - PHP Object Injection vulnerability — Yacht Rental 9.8 Critical 2026-10-10
CVE-2026-62053 WordPress Wine House theme <= 3.20 - PHP Object Injection vulnerability — Wine House 9.8 Critical 2026-10-10
CVE-2026-62052 WordPress Tipsy theme <= 1.6 - PHP Object Injection vulnerability — Tipsy 9.8 Critical 2026-10-10
CVE-2026-62051 WordPress Stargaze theme <= 1.10 - PHP Object Injection vulnerability — Stargaze 9.8 Critical 2026-10-10
CVE-2026-62050 WordPress Splendour theme <= 1.23 - PHP Object Injection vulnerability — Splendour 9.8 Critical 2026-10-10
CVE-2026-62021 WordPress Angio theme <= 1.1.1 - PHP Object Injection vulnerability — Angio 8.8 High 2026-10-10
CVE-2026-42723 WordPress CleanSkin theme <= 1.5.0 - PHP Object Injection vulnerability — CleanSkin 9.8 Critical 2026-10-10
CVE-2026-42719 WordPress Dynamic User Directory plugin <= 2.4 - PHP Object Injection vulnerability — Dynamic User Directory 9.8 Critical 2026-10-10
CVE-2026-42718 WordPress Booster for WooCommerce plugin <= 8.4.0 - PHP Object Injection vulnerability — Booster for WooCommerce 9.8 Critical 2026-10-10
CVE-2026-42716 WordPress Payever - WooCommerce Gateway plugin <= 4.8.2 - PHP Object Injection vulnerability — Payever - WooCommerce Gateway 9.8 Critical 2026-10-10
CVE-2026-104398 WordPress AFFI – Affiliate Marketing for WooCommerce plugin <= 1.0.10 - PHP Object Injection vulnerability — AFFI – Affiliate Marketing for WooCommerce 9.8 Critical 2026-10-10
CVE-2026-62044 WordPress Super Video Player plugin <= 1.8.13 - PHP Object Injection vulnerability — Super Video Player 7.2 High 2026-10-10
CVE-2026-94676 WordPress Tainacan plugin <= 1.3.0 - PHP Object Injection vulnerability — Tainacan 7.2 High 2026-10-10
CVE-2026-105885 WordPress Slider by 10Web plugin <= 1.2.62 - PHP Object Injection vulnerability — Slider by 10Web 8.8 High 2026-10-10
CVE-2026-62045 WordPress Booklovers theme <= 2.13.0 - PHP Object Injection vulnerability — Booklovers 9.8 Critical 2026-10-10
CVE-2026-62046 WordPress Gutentype theme <= 2.1.12 - PHP Object Injection vulnerability — Gutentype 9.8 Critical 2026-10-10
CVE-2026-93945 WordPress Balance theme <= 1.12.0 - PHP Object Injection vulnerability — Balance 9.8 Critical 2026-10-10
CVE-2026-93944 WordPress Camelia theme <= 1.2.15 - PHP Object Injection vulnerability — Camelia 9.8 Critical 2026-10-10
CVE-2026-93941 WordPress Edema theme <= 1.2.2.2 - PHP Object Injection vulnerability — Edema 9.8 Critical 2026-10-10
CVE-2026-93940 WordPress Greeny theme <= 2.10.0 - PHP Object Injection vulnerability — Greeny 9.8 Critical 2026-10-10
CVE-2026-93942 WordPress Dwell theme <= 1.16.0 - PHP Object Injection vulnerability — Dwell 9.8 Critical 2026-10-10
CVE-2026-93943 WordPress Convex theme <= 1.16.0 - PHP Object Injection vulnerability — Convex 9.8 Critical 2026-10-10
CVE-2026-93938 WordPress Hogwords theme <= 1.2.7 - PHP Object Injection vulnerability — Hogwords 9.8 Critical 2026-10-10
CVE-2026-93935 WordPress Let's Play theme <= 1.1.15 - PHP Object Injection vulnerability — Let's Play 9.8 Critical 2026-10-10
CVE-2026-93936 WordPress IPharm theme <= 1.2.4 - PHP Object Injection vulnerability — IPharm 9.8 Critical 2026-10-10
CVE-2026-93937 WordPress Hygia theme <= 1.21.0 - PHP Object Injection vulnerability — Hygia 9.8 Critical 2026-10-10
CVE-2026-93934 WordPress Partiso theme <= 1.1.13 - PHP Object Injection vulnerability — Partiso 9.8 Critical 2026-10-10

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