Quick answers
- Is CVE-2026-63315 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-63315 being exploited in the wild.
- How severe is CVE-2026-63315?
- Informational severity, published 15 October 2026.
- Which products and versions are affected?
- Slican IPx before 6.62.0100.
- Is there a fix for CVE-2026-63315?
- Yes: fixed in IPx series 6.62.0100. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-63315 attacked?
- It is attacked with local access, in a network appliance.
- Am I affected by CVE-2026-63315?
- Check whether you run Slican IPx at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: IPx series 6.62.0100
Technical details
Temporary subscriber passwords used within the WebCTI service are stored in plaintext rather than hashed or encrypted in the backend database. An attacker with read access to the database (via SQL injection, insider access, or breach) can directly extract these credentials. This affects the IPx telephone exchange series and has been patched in version 6.62.0100.
Affected products
- Slican IPx before 6.62.0100
Timeline
- 2026-10-15: disclosed
- 2026: patched: IPx series version 6.62.0100