# CVE-2006-0657: Cross-site scripting in n/a

> Authenticated users can inject scripts or code via username and password fields, leading to data corruption or code execution.

- **Severity:** Low 3.5 (`AV:N/AC:M/Au:S/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:** Not needed
- **Fix available:** No
- **Published:** 13 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4fwm-9mgp-g3cv

## What is CVE-2006-0657?

CVE-2006-0657 is a low-severity cross-site scripting vulnerability in n/a, published on 13 Feb 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Cross-site scripting (XSS) vulnerability in Softcomplex PHP Event Calendar 1.5 allows remote authenticated users to inject arbitrary web script or HTML, and corrupt data, via the (1) username and (2) password parameters, which are not sanitized before being written to users.php.  NOTE: while this issue was originally reported as XSS, the primary issue might be direct static code injection with resultant XSS.

## Which versions are affected by CVE-2006-0657?

It affects 1 product.


Products: Softcomplex Php Event Calendar.

## How do I fix CVE-2006-0657?

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

## Is CVE-2006-0657 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-3684](https://insights.sbomify.com/CVE-2006-3684/): Code injection in n/a (high 7.5)
- [CVE-2006-4825](https://insights.sbomify.com/CVE-2006-4825/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-0657 and fix it if it is affected.

What it is: CVE-2006-0657 is a low-severity cross-site scripting vulnerability in n/a, published on 13 Feb 2006. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-0657 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-2006-0657/ (Markdown: https://insights.sbomify.com/CVE-2006-0657/index.md)
```

## Sources

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

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