# CVE-2024-26136: kedi ElectronCord's Discord Token is public

> Attackers can access the Discord account token exposed in the configuration file to take over the account and read sensitive 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:** 20 Feb 2024
- **Updated:** 28 Aug 2024

## What is CVE-2024-26136?

CVE-2024-26136 is a high-severity vulnerability in kedi ElectronCord, published on 20 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

kedi ElectronCord is a bot management tool for Discord. Commit aaaeaf4e6c99893827b2eea4dd02f755e1e24041 exposes an account access token in the `config.json` file. Malicious actors could potentially exploit this vulnerability to gain unauthorized access to sensitive information or perform malicious actions on behalf of the repository owner. As of time of publication, it is unknown whether the owner of the repository has rotated the token or taken other mitigation steps aside from informing users of the situation.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2024-26136?

It affects 1 product.


Products: Openjsf Electroncord.

## How do I fix CVE-2024-26136?

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

## Is CVE-2024-26136 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-26136 and fix it if it is affected.

What it is: CVE-2024-26136 is a high-severity vulnerability in kedi ElectronCord, published on 20 Feb 2024. 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-2024-26136 in the wild and no public exploit code.

Affected product: kedi ElectronCord. 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-2024-26136/ (Markdown: https://insights.sbomify.com/CVE-2024-26136/index.md)
```

## Sources

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

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