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-62025 WordPress JobSearch plugin < 3.0.8 - PHP Object Injection vulnerability — JobSearch 9.8 Critical2025-10-22
CVE-2025-62008 WordPress Product Table For WooCommerce plugin <= 1.2.4 - PHP Object Injection vulnerability — Product Table For WooCommerce 8.8 High2025-10-22
CVE-2025-60232 WordPress KBx Pro Ultimate plugin <= 8.0.5 - PHP Object Injection vulnerability — KBx Pro Ultimate 9.8 Critical2025-10-22
CVE-2025-60238 WordPress UNIVERSAM plugin <= 9.04.02 - PHP Object Injection vulnerability — UNIVERSAM 9.8 Critical2025-10-22
CVE-2025-60234 WordPress Single Property theme <= 2.8 - PHP Object Injection vulnerability — Single Property 8.8 High2025-10-22
CVE-2025-60228 WordPress Knowledge Base theme <= 2.9 - PHP Object Injection vulnerability — Knowledge Base 8.8 High2025-10-22
CVE-2025-60224 WordPress Subscribe to Download plugin <= 2.0.9 - PHP Object Injection vulnerability — Subscribe to Download 9.8 Critical2025-10-22
CVE-2025-60225 WordPress BugsPatrol theme <= 1.5.0 - PHP Object Injection vulnerability — BugsPatrol 9.8 Critical2025-10-22
CVE-2025-60226 WordPress White Rabbit theme <= 1.5.2 - PHP Object Injection vulnerability — White Rabbit 9.8 Critical2025-10-22
CVE-2025-60221 WordPress Captivate Sync Plugin <= 3.0.3 - PHP Object Injection Vulnerability — Captivate Sync 9.8 Critical2025-10-22
CVE-2025-60216 WordPress Addison theme < 1.4.8 - PHP Object Injection vulnerability — Addison 9.8 Critical2025-10-22
CVE-2025-60214 WordPress Goldenblatt theme < 1.3.0 - PHP Object Injection vulnerability — Goldenblatt 9.8 Critical2025-10-22
CVE-2025-60212 WordPress VEDA Theme <= 4.2 - PHP Object Injection Vulnerability — VEDA 8.8 High2025-10-22
CVE-2025-60213 WordPress Scape theme <= 1.5.13 - PHP Object Injection vulnerability — Scape 9.8 Critical2025-10-22
CVE-2025-60215 WordPress Kriya theme <= 3.4 - PHP Object Injection Vulnerability — Kriya 8.8 High2025-10-22
CVE-2025-60210 WordPress Everest Forms - Frontend Listing plugin <= 1.0.5 - PHP Object Injection Vulnerability — Everest Forms - Frontend Listing 9.8 Critical2025-10-22
CVE-2025-60209 WordPress Connector for Gravity Forms and Google Sheets plugin <= 1.2.6 - PHP Object Injection vulnerability — Connector for Gravity Forms and Google Sheets 9.8 Critical2025-10-22
CVE-2025-60039 WordPress Noisa theme <= 2.6.0 - PHP Object Injection vulnerability — Noisa 9.8 Critical2025-10-22
CVE-2025-59007 WordPress TF Woo Product Grid Addon For Elementor Plugin <= 1.0.1 - Deserialization of untrusted data Vulnerability — TF Woo Product Grid Addon For Elementor 9.8 Critical2025-10-22
CVE-2025-52737 WordPress WP Store Locator plugin <= 2.2.260 - PHP Object Injection vulnerability — WP Store Locator 8.8 High2025-10-22
CVE-2025-52740 WordPress Boldermail Plugin <= 2.4.0 - PHP Object Injection Vulnerability — Boldermail 8.8 High2025-10-22
CVE-2025-49380 WordPress WooCommerce Vehicle Parts Finder plugin <= 3.7 - PHP Object Injection vulnerability — WooCommerce Vehicle Parts Finder 9.8 Critical2025-10-22
CVE-2025-31634 WordPress Insurance theme <= 3.5 - PHP Object Injection Vulnerability — Insurance 8.8 High2025-10-22
CVE-2025-32283 WordPress Solar Energy theme <= 3.5 - PHP Object Injection Vulnerability — Solar Energy 8.8 High2025-10-22
CVE-2025-11938 ChurchCRM setup.php deserialization — ChurchCRM 5.6 Medium2025-10-19
CVE-2017-20208 RegistrationMagic - Custom Registration Forms <= 3.7.9.2 - PHP Object Injection — RegistrationMagic – Custom Registration Forms, User Registration, Payment, and User Login 9.8 Critical2025-10-18
CVE-2017-20207 Flickr Gallery <= 1.5.2 - Unauthenticated PHP Object Injection — Flickr Gallery 9.8 Critical2025-10-18
CVE-2017-20206 Appointments <= 2.2.1 - Unauthenticated PHP Object Injection — Appointments 9.8 Critical2025-10-18
CVE-2025-62515 Remote Code Execution by Pickle Deserialization via FlightServer in pyquokka — quokka 9.8 Critical2025-10-17
CVE-2025-62419 DataEase vulnerable to JDBC URL injection in DB2 and MongoDB data source configuration — dataease 9.8AICriticalAI2025-10-17

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