Unauthorized API charges via hardcoded Google Maps key
Published May 21, 2026 · Updated May 21, 2026
Hard-coded credentials in Open ISES Tickets before 3.44.2 allow remote attackers to obtain a Google Maps API key from tables.php. tables.php embeds the key directly in application source committed to the public repository instead of loading an operator-supplied secret. Repository read access is sufficient to recover the key and submit Google Maps Platform requests billed to the owning cloud project.
Summary
What happened
Hard-coded credentials in Open ISES Tickets before 3.44.2 allow remote attackers to obtain a Google Maps API key from tables.php. tables.php embeds the key directly in application source committed to the public repository instead of loading an operator-supplied secret. Repository read access is sufficient to recover the key and submit Google Maps Platform requests billed to the owning cloud project.
The record
- CVE
- CVE-2026-48245
- Published
- May 21, 2026
- Updated
- May 21, 2026
- Vendor
- Open ISES
- Product
- Tickets CAD
- Classifications
- CWE-798, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 21, 2026CVE publishedPublication date reported by the CVE source.
- May 21, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.44.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo