# CVE-2026-48243: Open ISES Tickets < 3.44.2 Hardcoded WhitePages API Key in wp1.php

> Attackers can extract a hardcoded API key from the source code to make unauthorized third-party API calls, impacting the plugin owner's account.

- **Severity:** Medium 6.9 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 May 2026
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-ff8w-m7v9-pp77

## What is CVE-2026-48243?

CVE-2026-48243 is a medium-severity vulnerability in Open ISES Tickets, published on 21 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2026-48243?


## How do I fix CVE-2026-48243?

No fix has been published for CVE-2026-48243 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-48243 being exploited?

There is no known exploitation of CVE-2026-48243 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48243 and fix it if it is affected.

What it is: CVE-2026-48243 is a medium-severity vulnerability in Open ISES Tickets, published on 21 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-48243 in the wild and no public exploit code.

Affected product: Open ISES Tickets. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-48243/ (Markdown: https://insights.sbomify.com/CVE-2026-48243/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48243
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48243
- OSV: https://osv.dev/vulnerability/CVE-2026-48243

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-48243/
Summaries are generated and may contain mistakes; the official description above is the record.