VulnerabilityPublished 13 May 2026

CVE-2026-25107: ELECOM WRC-X1800GS-B · Use of Hard-coded Cryptographic Key

Affects ELECOM WRC-X1800GS-BSource CVE Database V5

Compare

Not known to be exploited · CVSS 6.5 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.0 base score

6.5Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: High
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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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 13 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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

Affected software

Product	Affected	Fixed in
ELECOM CO.,LTD.WRC-X1800GS-B	Affected =v1.19 and earlier	Fixed in–
ELECOM CO.,LTD.WRC-X3000GS2-B	Affected =v1.09 and earlier	Fixed in–
ELECOM CO.,LTD.WRC-X3000GS2-W	Affected =v1.09 and earlier	Fixed in–
ELECOM CO.,LTD.WRC-X3000GS2A-B	Affected =v1.09 and earlier	Fixed in–
ELECOM CO.,LTD.WRC-X3000GST2-B	Affected =v1.06 and earlier	Fixed in–
ELECOM CO.,LTD.WRC-X1800GSA-B	Affected =v1.19 and earlier	Fixed in–

AI-suggested

Until an official fix is available, administrators should avoid importing configuration files from untrusted sources and verify the authenticity of backup files before applying them.

Description

ELECOM CO. ,LTD. WRC-X1800GS-B wireless LAN access points use a hard-coded cryptographic key for encrypting configuration file backups. An attacker who knows this key can modify a configuration file and potentially trick an administrator into applying a malicious configuration. This vulnerability affects versions v1.19 and earlier. The CVSS score is 6.5, indicating a medium severity level. No official patch or remediation guidance is currently available from the vendor. There are no known exploits in the wild at this time.

Impact

The vulnerability enables an attacker to modify encrypted configuration backups, potentially leading to unauthorized configuration changes if an administrator imports a maliciously altered file. This can impact the integrity of the device configuration but does not directly affect confidentiality or availability. The CVSS vector indicates no confidentiality impact, high integrity impact, and no availability impact.

Summary

The ELECOM WRC-X1800GS-B device uses a hard-coded cryptographic key to encrypt backup configuration files. This design flaw allows an attacker with knowledge of the key to tamper with configuration files. If an administrator applies a crafted configuration file, the device could be misconfigured or compromised. The vulnerability affects firmware versions v1.19 and earlier.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 20 May 2026, 19:11 UTC

Technical details

References

Community reviews

Related threats