# CVE-2026-24449: Hardcoded credentials in WRC-X1500GS-B

> Attackers can easily calculate initial passwords from system information, leading to unauthorized access to ELECOM routers.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Feb 2026
- **Updated:** 3 Feb 2026
- **Also known as:** GHSA-xcmw-w3hr-qh6q

## What is CVE-2026-24449?

CVE-2026-24449 is a medium-severity vulnerability in ELECOM CO.,LTD. WRC-X1500GS-B, published on 3 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

For WRC-X1500GS-B and WRC-X1500GSA-B, the initial passwords can be calculated easily from the system information.

Weakness: CWE-1391 (Use of Weak Credentials)

## Which versions are affected by CVE-2026-24449?

It affects 2 products.


Products: Elecom Wrc-X1500gs-B Firmware, Elecom Wrc-X1500gsa-B Firmware.

## How do I fix CVE-2026-24449?

No fix has been published for CVE-2026-24449 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-24449 being exploited?

There is no known exploitation of CVE-2026-24449 in the wild and no public exploit code.

## Other vulnerabilities in ELECOM CO.,LTD. WRC-X1500GS-B

- [CVE-2026-22550](https://insights.sbomify.com/CVE-2026-22550/): Command injection in WRC-X1500GS-B (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-24449 and fix it if it is affected.

What it is: CVE-2026-24449 is a medium-severity vulnerability in ELECOM CO.,LTD. WRC-X1500GS-B, published on 3 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-24449 in the wild and no public exploit code.

Affected product: ELECOM CO.,LTD. WRC-X1500GS-B. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-24449/ (Markdown: https://insights.sbomify.com/CVE-2026-24449/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-24449
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-24449
- OSV: https://osv.dev/vulnerability/CVE-2026-24449

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-24449/
Summaries are generated and may contain mistakes; the official description above is the record.