# CVE-2005-0474: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands via a crafted session cookie in WebCalendar, potentially compromising database integrity and confidentiality.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/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:** 19 Feb 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4mmm-jj36-wmc5

## What is CVE-2005-0474?

CVE-2005-0474 is a medium-severity SQL injection vulnerability in n/a, published on 19 Feb 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SQL injection vulnerability in the user_valid_crypt function in user.php in WebCalendar 0.9.45 allows remote attackers to execute arbitrary SQL commands via an encoded webcalendar_session cookie.

## Which versions are affected by CVE-2005-0474?

It affects 1 product.


Products: Webcalendar Webcalendar.

## How do I fix CVE-2005-0474?

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

## Is CVE-2005-0474 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-1343](https://insights.sbomify.com/CVE-2007-1343/): Code injection in n/a (high 7.5)
- [CVE-2005-3984](https://insights.sbomify.com/CVE-2005-3984/): SQL injection in n/a (high 7.5)
- [CVE-2005-3949](https://insights.sbomify.com/CVE-2005-3949/): SQL injection in n/a (high 7.5)
- [CVE-2005-2717](https://insights.sbomify.com/CVE-2005-2717/): Code injection in n/a (high 7.5)
- [CVE-2005-2320](https://insights.sbomify.com/CVE-2005-2320/): Missing authorization in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-0474 and fix it if it is affected.

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

## Sources

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

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