CVE-2025-7216VulnerabilityPublished 9 Jul 2025

CVE-2025-7216: lty628 Aidigu · Deserialization

Affects lty628 AidiguSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
lty628 Aidigu	Affected =1.8.0 =1.8.1 =1.8.2	Fixed in–

AI-suggested

European organizations should immediately audit their environments to identify any deployments of lty628 Aidigu versions 1.8.0, 1.8.1, or 1.8.2. In the absence of an official patch, organizations should consider the following specific mitigations: 1) Disable or restrict the use of the 'rememberMe' functionality if feasible, to prevent deserialization of untrusted input. 2) Implement Web Application Firewall (WAF) rules to detect and block suspicious serialized payloads targeting the checkUserCookie function or the 'rememberMe' parameter. 3) Employ input validation and sanitization at the application level to reject malformed or unexpected serialized data. 4) Restrict network access to the affected application components, limiting exposure to trusted internal networks where possible. 5) Monitor application logs and network traffic for anomalous activity indicative of exploitation attempts, such as unusual serialized data patterns or unexpected requests to the vulnerable endpoint. 6) Prepare for rapid deployment of official patches once released by the vendor and maintain close communication with lty628 for updates. 7) Conduct security awareness training for developers and administrators on the risks of insecure deserialization and secure coding practices. These targeted actions go beyond generic advice by focusing on the specific vulnerable parameter and function, leveraging network controls, and emphasizing proactive detection.

Description

A vulnerability, which was classified as critical, was found in lty628 Aidigu up to 1.8.2. This affects the function checkUserCookie of the file /application/common.php of the component PHP Object Handler. The manipulation of the argument rememberMe leads to deserialization. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.

Impact

For European organizations using lty628 Aidigu versions 1.8.0 through 1.8.2, this vulnerability poses a tangible risk of remote compromise. Successful exploitation could allow attackers to execute arbitrary code on affected servers, potentially leading to unauthorized access, data leakage, or disruption of services. Given that the vulnerability does not require authentication or user interaction, attackers can target exposed web applications directly over the network. This increases the risk for public-facing services, especially those handling sensitive user data or critical business functions. In sectors such as finance, healthcare, and government, where data confidentiality and service availability are paramount, exploitation could result in regulatory non-compliance, reputational damage, and operational downtime. Moreover, the disclosed exploit details may accelerate attack attempts, necessitating urgent attention. The medium severity rating suggests that while the vulnerability is serious, the overall impact might be mitigated by existing security controls or the specific deployment context. However, organizations lacking robust network defenses or running unpatched versions are at higher risk. The absence of known exploits in the wild currently provides a limited window for remediation before active attacks emerge.

References

Community reviews

Loading reviews…