Approved changes feed: RSS · Atom
cpe:2.3:a:tktchurch:website:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Tktchurch (46c626fd-9d5f-5e6f-a083-5b0e2b0c2d6e) |
|---|---|
| Product | Website (d34139e8-6ddf-57c6-b79f-d91d243946cf) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2023-36817 |
vulnerable | 2026-06-08 06:08:13.541820 |
The King's Temple Church website Leaked Stripe API Key in Public Code Repository
HIGH (7.5)
`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.
Published: 2023-07-03T17:54:35.894Z
Updated: 2024-11-06T16:55:02.330Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.