Quick answers
- Is CVE-2026-48241 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-48241 being exploited in the wild.
- How severe is CVE-2026-48241?
- 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-48241?
- A patch was published on 2026-04-01: Fixes committed to repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-48241 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-48241?
- 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 suffer from the use of hardcoded credentials (CWE-798) within the 'loader.php' utility. The MySQL database username, password, and database name were committed directly to the public source repository. An unauthenticated remote attacker can retrieve these credentials by reading the file on a deployed instance or via the public source tree. If the database port is exposed to the network, the attacker can use these credentials to gain full administrative access to the database, leading to unauthorized data exfiltration or modification. The issue was resolved in version 3.44.2 by removing the hardcoded secrets.
Affected products
- Open ISES Tickets before 3.44.2
Timeline
- 2026-04-01: patched: Fixes committed to repository
- 2026-04-02: advisory: Release v3.44.2 published
- 2026-05-21: disclosed: CVE-2026-48241 published