CVE-2026-48243: Open ISES Tickets < 3.44.2 Hardcoded WhitePages API Key in wp1.php
Open ISES Tickets before 3.44.2 embeds a hardcoded WhitePages reverse-phone API key in wp1.php that is committed to the public source repository. Any actor with read access to the source tree can extract the key and use it to make third-party API calls billed to or rate-limited against the original owner's WhitePages account.
Security readout for executives and security teams
Plain-English summary
Open ISES Tickets versions before 3.44.2 exposed a WhitePages API key in publicly accessible source code. Anyone who obtained it could consume the account’s API allowance, cause unexpected charges, or exhaust rate limits. The supplied sources do not indicate compromise of ticket data or systems.
Executive priority
Address promptly as a credential-exposure and cost-control issue. Prioritize revocation over upgrade alone because removing the key from current code cannot invalidate copies already obtained. Escalate if billing anomalies, quota exhaustion, or unexplained WhitePages activity are found.
Technical view
CVE-2026-48243 is a CWE-798 hardcoded-credential flaw in wp1.php. The embedded WhitePages reverse-phone API key was committed to the public repository and required no privileges, interaction, or attack complexity to obtain. CVSS 4.0 scores it 6.9. Release 3.44.2 and its associated commit are identified as the patch.
Likely exposure
Deployments or source copies from before 3.44.2 may contain the credential. Exposure also extends to repository history, forks, archives, build artifacts, and developer workstations containing the vulnerable source. Actual organizational exposure depends on whether the embedded key belonged to an active WhitePages account.
Exploitation context
The key could be reused for third-party WhitePages API requests charged to, or rate-limited against, its owner. KEV is false, and the supplied sources provide no evidence of active exploitation. Public source exposure nevertheless means the credential should be treated as potentially disclosed.
Researcher notes
The narrative identifies all versions before 3.44.2, while the supplied affected-data entry lists version "0" with default status unaffected. This inconsistency limits precise machine-readable range conclusions. The documented impact concerns an external API credential; no source establishes application compromise, sensitive ticket disclosure, or active abuse.
Mitigation direction
Upgrade Open ISES Tickets to version 3.44.2 or later.
Revoke the exposed WhitePages API key and issue a replacement if still required.
Review repository history, forks, archives, and artifacts for retained credential copies.
Restrict replacement credentials using provider-supported scope, quota, and monitoring controls.
Check current vendor guidance for any additional remediation requirements.
Validation and detection
Identify every Open ISES Tickets deployment and confirm its installed version.
Search authorized source inventories and artifacts for the exposed credential without disclosing its value.
Confirm the original WhitePages key is revoked or otherwise unusable.
Review WhitePages account activity, billing, and quota usage for unexplained requests.
Verify updated application functionality uses no credential embedded in committed source.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · medium confidence lookup
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.
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.
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-798 · source CWE mapping
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.