# CVE-2003-0736: Cross-site scripting in n/a

> Remote attackers can execute arbitrary web script via multiple parameters in phpWebSite modules, requiring user interaction to trigger.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **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:** 4 Sep 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-jcpm-q5g4-h5jc

## What is CVE-2003-0736?

CVE-2003-0736 is a medium-severity cross-site scripting vulnerability in n/a, published on 4 Sep 2003. 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

Multiple cross-site scripting (XSS) vulnerabilities in phpWebSite 0.9.x and earlier allow remote attackers to execute arbitrary web script via (1) the day parameter in the calendar module, (2) the fatcat_id parameter in the fatcat module, (3) the PAGE_id parameter in the pagemaster module, (4) the PDA_limit parameter in the search, and (5) possibly other parameters in the calendar, fatcat, and pagemaster modules.

## Which versions are affected by CVE-2003-0736?

It affects 1 product.


Products: Phpwebsite Phpwebsite.

## How do I fix CVE-2003-0736?

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

## Is CVE-2003-0736 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-0736 exists.

Public exploit code:

- phpWebSite 0.7.3/0.8.2/0.8.3/0.9.2 Calendar Module - 'day' Cross-Site Scripting (exploitdb)
- phpWebSite 0.7.3/0.8.2/0.8.3/0.9.2 fatcat Module - 'fatcat_id' Cross-Site Scripting (exploitdb)
- phpWebSite 0.7.3/0.8.2/0.8.3/0.9.2 pagemaster Module - 'PAGE_id' Cross-Site Scripting (exploitdb)
- phpWebSite 0.7.3/0.8.2/0.8.3/0.9.2 earch Module - 'PDA_limit' Cross-Site Scripting (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2003-0738](https://insights.sbomify.com/CVE-2003-0738/): Denial of service in n/a (high 7.8)
- [CVE-2006-5234](https://insights.sbomify.com/CVE-2006-5234/): Code injection in n/a (high 7.5)
- [CVE-2005-4792](https://insights.sbomify.com/CVE-2005-4792/): SQL injection in n/a (high 7.5)
- [CVE-2006-1819](https://insights.sbomify.com/CVE-2006-1819/): Path traversal in n/a (high 7.5)
- [CVE-2006-1330](https://insights.sbomify.com/CVE-2006-1330/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-0736 and fix it if it is affected.

What it is: CVE-2003-0736 is a medium-severity cross-site scripting vulnerability in n/a, published on 4 Sep 2003. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-0736 exists.

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-2003-0736/ (Markdown: https://insights.sbomify.com/CVE-2003-0736/index.md)
```

## Sources

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

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