Security readout for executives and security teams
Plain-English summary
Open ISES Tickets before 3.44.2 exposes a Google Maps API key in public source code. Anyone who obtains it may charge Google Maps requests to the key owner's cloud project, creating unexpected costs and potential service-quota consumption. The supplied evidence does not indicate compromise of ticket data or systems.
Executive priority
Address promptly as a cloud-cost and quota-abuse risk, especially if the project is billable or the key remains active. Prioritize key revocation or rotation alongside the upgrade. Escalate if monitoring shows unexplained Maps usage or charges; the supplied evidence does not support emergency incident status by itself.
Technical view
CVE-2026-48245 is a CWE-798 hardcoded-credential issue in tables.php. It is remotely discoverable without privileges or user interaction because the key was committed to a public repository. CVSS 4.0 is 6.9. Version 3.44.2 is identified as the corrective release; the supplied bundle does not establish whether upgrading alone revokes previously exposed keys.
Likely exposure
Deployments or source copies from before 3.44.2 may contain the exposed key. The primary exposure belongs to the Google Cloud project associated with that key. Public repository history can preserve a disclosed secret after code removal, so historical exposure should be assumed until the key is verified or replaced.
Exploitation context
The weakness requires only obtaining the published key and using it for Google Maps Platform requests. No KEV listing or supplied source establishes active exploitation. Actual financial impact depends on the key's continued validity, API restrictions, quotas, billing controls, and monitoring.
Researcher notes
The stated vector is AV:N/AC:L/AT:N/PR:N/UI:N with low confidentiality impact and no stated integrity, availability, or downstream impacts. Scope assessment should distinguish the vulnerable application version from the separate lifecycle of the leaked cloud credential. The supplied affected-version metadata is inconsistent—versions lists "0" while the description says before 3.44.2—so use the description and corrective release cautiously.
Mitigation direction
- Upgrade Open ISES Tickets to version 3.44.2 or later.
- Revoke or rotate the exposed Google Maps API key.
- Restrict replacement keys by API, application, and permitted origin where appropriate.
- Review Google Cloud quotas, budgets, alerts, and vendor guidance.
Validation and detection
- Search deployed files and retained source copies for the disclosed key.
- Confirm the old key is disabled or no longer authorizes requests.
- Verify production runs version 3.44.2 or later.
- Review Google Maps usage, billing, and audit data for unexpected activity.
- Confirm replacement-key restrictions and budget alerts are active.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-798: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-48245 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.9 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N——VulnCheckCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4VulnCheckVulnerability scoring details
Base CVSS 4.0 score
6.9MediumVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/openises/tickets/releases/tag/v3.44.2CVE reference, VulnCheck · release-notes
- https://github.com/openises/tickets/commit/ecfeb406a016766cae81c749e14b5145a9f2dbffCVE reference, VulnCheck · patch
- https://www.vulncheck.com/advisories/open-ises-tickets-hardcoded-google-maps-api-key-in-tables-phpCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of Hard-coded Credentials
Use of Hard-coded Credentials represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.