# CVE-2023-36817: The King's Temple Church website Leaked Stripe API Key in Public Code Repository

> A Stripe API key was hardcoded in a public repository, allowing attackers to perform transactions and access customer data.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jul 2023
- **Updated:** 6 Nov 2024
- **Also known as:** GHSA-x3m6-5hmf-5x3w

## What is CVE-2023-36817?

CVE-2023-36817 is a high-severity vulnerability in tktchurch website, published on 3 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

`tktchurch/website` contains the codebase for The King's Temple Church website. In version 0.1.0, a Stripe API key was found in the public code repository of the church's project. This sensitive information was unintentionally committed and subsequently exposed in the codebase. If an unauthorized party gains access to this key, they could potentially carry out transactions on behalf of the organization, leading to financial losses. Additionally, they could access sensitive customer information, leading to privacy violations and potential legal implications. The affected component is the codebase of our project, specifically the file(s) where the Stripe API key is embedded. The key should have been stored securely, and not committed to the codebase. The maintainers plan to revoke the leaked Stripe API key immediately, generate a new one, and not commit the key to the codebase.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2023-36817?

It affects 1 product.


Products: Kingstemple the King\'s Temple Church Website.

## How do I fix CVE-2023-36817?

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

## Is CVE-2023-36817 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-36817 and fix it if it is affected.

What it is: CVE-2023-36817 is a high-severity vulnerability in tktchurch website, published on 3 Jul 2023. 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-2023-36817 in the wild and no public exploit code.

Affected product: tktchurch website. 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-2023-36817/ (Markdown: https://insights.sbomify.com/CVE-2023-36817/index.md)
```

## Sources

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

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