# CVE-2009-0247: Cross-site scripting in n/a

> Remote attackers can execute cross-site scripting attacks in 53KF Web IM by sending crafted messages, bypassing client-side protections.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 22 Jan 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-889v-735q-h2mp

## What is CVE-2009-0247?

CVE-2009-0247 is a medium-severity cross-site scripting vulnerability in n/a, published on 22 Jan 2009. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The server for 53KF Web IM 2009 Home, Professional, and Enterprise editions relies on client-side protection mechanisms against cross-site scripting (XSS), which allows remote attackers to conduct XSS attacks by using a modified client to send a crafted IM message, related to the msg variable.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2009-0247?

It affects 1 product.


Products: 53kf Web Im 2009.

## How do I fix CVE-2009-0247?

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

## Is CVE-2009-0247 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-0247 and fix it if it is affected.

What it is: CVE-2009-0247 is a medium-severity cross-site scripting vulnerability in n/a, published on 22 Jan 2009. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2009-0247 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-2009-0247/ (Markdown: https://insights.sbomify.com/CVE-2009-0247/index.md)
```

## Sources

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

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