Quick answers
- Is CVE-2026-48243 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-48243 being exploited in the wild.
- How severe is CVE-2026-48243?
- Medium severity, with a CVSS score of 5.3, published 21 May 2026.
- Which products and versions are affected?
- Open ISES Tickets before 3.44.2.
- Is there a fix for CVE-2026-48243?
- A patch was published on 2026-04-01: Fix committed to repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-48243 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-48243?
- Check whether you run Open ISES Tickets 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.
Technical details
A hardcoded WhitePages reverse-phone API key was discovered in the 'wp1.php' file of Open ISES Tickets versions prior to 3.44.2. Because this key was committed to a public version control repository, it is accessible to any actor with read access to the source tree. An attacker can extract this credential and perform API calls that are billed to or rate-limited against the legitimate owner's account. This vulnerability is classified as CWE-798 (Use of Hard-coded Credentials). The issue was remediated in version 3.44.2 by removing the secret from the codebase.
Affected products
- Open ISES Tickets before 3.44.2
Timeline
- 2026-04-01: patched: Fix committed to repository
- 2026-04-02: advisory: Release v3.44.2 published
- 2026-05-21: disclosed: CVE-2026-48243 published