# CVE-2015-0889: Other in n/a

> Remote attackers can delete or write files to execute arbitrary code in KENT-WEB Joyful Note via article vectors.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 28 Feb 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-27xp-xm97-jqhm

## What is CVE-2015-0889?

CVE-2015-0889 is a high-severity vulnerability in n/a, published on 28 Feb 2015. It can be exploited over the network.

### Official description

KENT-WEB Joyful Note before 5.3 allows remote attackers to delete files or write to files, and consequently execute arbitrary code, via vectors involving an article.

## Which versions are affected by CVE-2015-0889?

It affects 1 product.


Products: Kent-Web Joyful Note.

## How do I fix CVE-2015-0889?

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

## Is CVE-2015-0889 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-0812](https://insights.sbomify.com/CVE-2014-0812/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-0889 and fix it if it is affected.

What it is: CVE-2015-0889 is a high-severity vulnerability in n/a, published on 28 Feb 2015. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2015-0889 in the wild and no public exploit code.

Affected product: n/a. 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-2015-0889/ (Markdown: https://insights.sbomify.com/CVE-2015-0889/index.md)
```

## Sources

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

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