# CVE-2018-0509: Cross-site request forgery in epg search result viewer(kkcald)

> Attackers can hijack administrator sessions in the EPG search result viewer via cross-site request forgery, requiring an upgrade to secure the application.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-6vxj-jr6j-cqqx

## What is CVE-2018-0509?

CVE-2018-0509 is a high-severity vulnerability in epg search result viewer(kkcald), published on 1 Feb 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Cross-site request forgery (CSRF) vulnerability in epg search result viewer (kkcald) 0.7.21 and earlier allows an attacker to hijack the authentication of administrators via unspecified vectors.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2018-0509?

It affects 1 product.


Products: Kkcald Project Kkcald.

## How do I fix CVE-2018-0509?

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

## Is CVE-2018-0509 being exploited?

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

## Other vulnerabilities in epg search result viewer(kkcald)

- [CVE-2018-0510](https://insights.sbomify.com/CVE-2018-0510/): Memory corruption in epg search result viewer(kkcald) (critical 9.8)
- [CVE-2018-0508](https://insights.sbomify.com/CVE-2018-0508/): Cross-site scripting in epg search result viewer(kkcald) (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-0509 and fix it if it is affected.

What it is: CVE-2018-0509 is a high-severity vulnerability in epg search result viewer(kkcald), published on 1 Feb 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-0509 in the wild and no public exploit code.

Affected product: epg search result viewer(kkcald). 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-2018-0509/ (Markdown: https://insights.sbomify.com/CVE-2018-0509/index.md)
```

## Sources

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

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