CVE-2025-46267VulnerabilityPublished 22 Jul 2025

CVE-2025-46267: ELECOM WRC-BE36QS-B · Hidden functionality

Affects ELECOM WRC-BE36QS-BSource CVE Database V5

Not known to be exploited · CVSS 4.9 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

4.9Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
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: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
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: 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 22 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-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-BE36QS-B	Affected <=1.1.3	Fixed in–

AI-suggested

1. Restrict access to the router's WebGUI interface by implementing network segmentation and firewall rules to limit management access only to trusted administrative hosts and networks. 2. Enforce strong authentication mechanisms, including complex passwords and, if supported, multi-factor authentication (MFA) for WebGUI login to reduce the risk of credential compromise. 3. Monitor router management access logs for unusual login attempts or successful authentications from unexpected sources to detect potential misuse. 4. Disable or restrict any debug or developer modes if configurable via existing settings, even if hidden, to minimize attack surface. 5. Regularly update device firmware and monitor ELECOM's official channels for security advisories and patches addressing this vulnerability. 6. Consider replacing affected devices with alternative models from vendors with stronger security track records if patching is delayed or unavailable. 7. Implement network intrusion detection systems (NIDS) to identify anomalous traffic patterns that may indicate exploitation attempts related to this vulnerability. 8. Educate network administrators about the risks of credential theft and the importance of safeguarding access credentials to network devices.

Description

Hidden functionality issue exists in WRC-BE36QS-B and WRC-W701-B. If exploited, the product's hidden debug function may be enabled by a remote attacker who can log in to WebGUI.

Impact

For European organizations, this vulnerability poses a moderate risk, especially for enterprises and service providers using ELECOM WRC-BE36QS-B or WRC-W701-B routers in their network infrastructure. If an attacker gains authenticated access to the router's WebGUI—potentially through credential theft, phishing, or insider threats—they could enable the hidden debug functionality, which may allow manipulation of router settings or facilitate lateral movement within the network. This could undermine the integrity of network traffic routing or security policies enforced by the device. While the vulnerability does not directly impact confidentiality or availability, the integrity compromise could lead to unauthorized configuration changes, weakening network defenses. Organizations relying on these devices for critical network functions or connected to sensitive systems could face increased risk of targeted attacks or data manipulation. Additionally, the absence of patches means organizations must rely on compensating controls until a fix is available. The medium severity rating suggests that while the threat is not immediately critical, it should be addressed promptly to prevent escalation or exploitation in multi-stage attacks.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 22 Jul 2025, 10:01 UTC

Technical details

References

Community reviews

Related threats