# CVE-2002-0739: Cross-site scripting in n/a

> Remote attackers can inject scripts via calendar entry previews to steal cookies, requiring user interaction to view the malicious entry.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** 26 Jul 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-94c8-2r24-j257

## What is CVE-2002-0739?

CVE-2002-0739 is a high-severity cross-site scripting vulnerability in n/a, published on 26 Jul 2002. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Cross-site scripting in PostCalendar 3.02 allows remote attackers to insert arbitrary HTML and script, and steal cookies, by modifying a calendar entry in its preview page.

## Which versions are affected by CVE-2002-0739?

It affects 1 product.


Products: Postnuke Software Foundation Postcalendar.

## How do I fix CVE-2002-0739?

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

## Is CVE-2002-0739 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-1787](https://insights.sbomify.com/CVE-2004-1787/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-0739 and fix it if it is affected.

What it is: CVE-2002-0739 is a high-severity cross-site scripting vulnerability in n/a, published on 26 Jul 2002. 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-2002-0739 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-2002-0739/ (Markdown: https://insights.sbomify.com/CVE-2002-0739/index.md)
```

## Sources

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

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