Quick answers
- Is CVE-2026-48242 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-48242 being exploited in the wild.
- How severe is CVE-2026-48242?
- High severity, with a CVSS score of 8.1, published 21 May 2026.
- Which products and versions are affected?
- Open ISES Tickets before 3.44.2.
- Is there a fix for CVE-2026-48242?
- 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-48242 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-48242?
- 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
Open ISES Tickets versions prior to 3.44.2 contain hardcoded MySQL database credentials (host, username, password, and database name) within the 'import_mdb.php' file. These credentials were committed to the public source code repository, making them accessible to any user. While the attack complexity is rated as high because the credentials must match a specific deployed environment, a remote attacker could leverage this information to gain direct access to the database. This bypasses standard authentication and allows for full data exfiltration or manipulation. The issue was addressed in version 3.44.2 by removing the hardcoded secrets.
Affected products
- Open ISES Tickets before 3.44.2
Timeline
- 2026-04-01: patched: Fix committed to repository
- 2026-04-02: advisory: Version 3.44.2 released
- 2026-05-21: disclosed: CVE published to NVD