VulnerabilityPublished 18 Aug 2025

CVE-2025-55585: TOTOLINK A3002R · Eval Injection

Source CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 11:07 UTC

CVSS 3.1 base score

6.5Medium

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

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, 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: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
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 impacted component.
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 on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Aug 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 26 Oct 2026.

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 or the CVSS exploit maturity 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

AI-suggested

To mitigate this vulnerability, European organizations and users of TOTOLINK A3002R routers should first verify their firmware version and avoid using the affected version 4.0.0-B20230531.1404. Until an official patch is released, users should consider the following specific actions: 1) Disable remote management interfaces to reduce exposure to external attackers. 2) Restrict network access to the router’s administrative interface to trusted IP addresses only. 3) Monitor router logs for unusual activity or unauthorized configuration changes. 4) Employ network segmentation to isolate vulnerable routers from critical systems. 5) Use strong, unique passwords for router administration to prevent unauthorized access. 6) Consider replacing the affected router with a model from a vendor with a strong security track record if patching is not imminent. 7) Stay informed through vendor advisories and apply firmware updates promptly once available. Additionally, network intrusion detection systems should be tuned to detect anomalous traffic patterns that could indicate exploitation attempts.

Description

TOTOLINK A3002R v4.0.0-B20230531.1404 was discovered to contain an eval injection vulnerability via the eval() function.

Impact

For European organizations, the impact of this vulnerability could be significant, especially for small businesses and home offices relying on TOTOLINK A3002R routers. Successful exploitation could lead to unauthorized access to the router's administrative interface, enabling attackers to alter network configurations, intercept or redirect traffic, and deploy further malware or lateral movement within the network. This could compromise confidentiality by exposing sensitive data, integrity by modifying network settings or firmware, and availability by disrupting network connectivity. Given the router’s role as a network gateway, exploitation could also facilitate man-in-the-middle attacks or persistent backdoors. While large enterprises may use more robust network equipment, smaller organizations and remote workers in Europe are likely to be more exposed. The absence of known exploits in the wild currently limits immediate risk, but the ease of exploitation inherent in eval injection vulnerabilities means that threat actors could develop exploits rapidly once details are public. The impact is compounded by the lack of an available patch, increasing the window of exposure.

CWE-95Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection') (opens in a new tab)
Variant weaknessLikelihood of exploit: MediumOWASP Top 10 A05:2025: Injection (opens in a new tab)
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes code syntax before using the input in a dynamic evaluation call (e.g. "eval").
Architecture and Design · Implementation · Refactoring
If possible, refactor your code so that it does not need to use eval() at all.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Implementation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180, CWE-181). Make sure that your application does not inadvertently decode the same input twice (CWE-174).
OWASP Cheat Sheets
Deserialization (opens in a new tab)
XML Security (opens in a new tab)
XML External Entity Prevention (opens in a new tab)
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
OWASP ASVS 4.0.3
V5.5.4 (opens in a new tab)
V5.2.4 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
Leverage Executable Code in Non-Executable Files (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/goldenGlow21/softwares_PoC/blob/main/A3002R_V4/Eval%20Injection/PoC.md (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 18 Aug 2025, 19:49 UTC

WeaknessesCWE-95

Technical details

References

Community reviews

Related threats