CVE-2025-36519VulnerabilityPublished 24 Jun 2025Updated 3 Feb 2026

CVE-2025-36519: ELECOM WRC-2533GST2 · Unrestricted File Upload

Affects ELECOM WRC-2533GST2Source CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.0 base score

4.3Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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: None: There is no loss of confidentiality within 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 24 Jun 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-26.

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
ELECOM CO.,LTD. WRC-2533GST2	Affected <=1.31	Fixed in–

AI-suggested

1. Apply firmware updates from ELECOM as soon as they are released to address this vulnerability. 2. Restrict administrative access to the routers by limiting management interfaces to trusted IP addresses or VPNs. 3. Enforce strong authentication mechanisms, including changing default credentials and implementing multi-factor authentication if supported. 4. Monitor router logs and network traffic for unusual file upload activities or unauthorized access attempts. 5. Segment network infrastructure to isolate critical devices and reduce the attack surface. 6. Disable or restrict file upload functionality if not required for normal operations. 7. Conduct regular security audits and vulnerability assessments on network devices. 8. Educate network administrators about the risks of this vulnerability and best practices for secure device management. 9. Consider deploying network intrusion detection systems capable of identifying anomalous behavior related to device compromise.

Description

Unrestricted upload of file with dangerous type issue exists in WRC-2533GST2, WRC-1167GST2, WRC-2533GST2, WRC-2533GS2V-B,WRC-2533GS2-B v1.69 and earlier, WRC-2533GS2-W, WRC-1167GST2, WRC-1167GS2-B, and WRC-1167GS2H-B. If a specially crafted file is uploaded by a remote authenticated attacker, arbitrary code may be executed on the product.

Impact

For European organizations, the primary impact of CVE-2025-36519 lies in the potential compromise of network infrastructure devices, specifically ELECOM wireless routers. Successful exploitation could allow attackers to execute arbitrary code, leading to unauthorized configuration changes, installation of malicious firmware, or use of the device as a pivot point for further attacks within the network. This undermines the integrity of network operations and could facilitate espionage, data exfiltration, or disruption of services indirectly. Organizations relying on these routers for critical connectivity or security segmentation may face increased risk of persistent intrusions. The requirement for authentication limits exposure but does not eliminate risk, especially if credential management is weak or default credentials are in use. Given the medium severity, the threat is moderate but could escalate if combined with other vulnerabilities or poor security practices. European entities in sectors such as telecommunications, manufacturing, or SMEs using ELECOM equipment should be particularly vigilant.

Summary

CVE-2025-36519 is a vulnerability identified in several ELECOM CO.,LTD. wireless router models, including WRC-2533GST2, WRC-1167GST2, and related variants, specifically in firmware versions 1.69 and earlier. The issue stems from insufficient validation on file uploads, allowing authenticated remote attackers to upload files with dangerous types unrestrictedly. This flaw can be exploited to execute arbitrary code on the device, compromising its integrity. The attack vector requires network access and valid credentials, but no additional user interaction is necessary. The vulnerability does not impact confidentiality or availability directly but poses a risk to device integrity and control. No public exploits have been reported yet, but the presence of arbitrary code execution potential makes it a significant concern. The CVSS 3.0 base score of 4.3 reflects the medium severity, factoring in network attack vector, low attack complexity, and required privileges. The vulnerability affects a range of ELECOM routers widely used in small to medium enterprise and possibly home environments. The lack of available patches at the time of reporting necessitates interim mitigations to reduce risk. Attackers exploiting this vulnerability could gain persistent control over affected devices, potentially using them as footholds for further network compromise or lateral movement.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Feb 2026, 08:36 UTC

Technical details

References

Community reviews

Related threats