# CVE-2006-0835: SQL injection in n/a

> Remote attackers can exploit SQL injection in MitriDAT Web Calendar Pro to modify database queries, causing denial of service.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-ccfj-vhr9-fqvq

## What is CVE-2006-0835?

CVE-2006-0835 is a high-severity SQL injection vulnerability in n/a, published on 22 Feb 2006. It can be exploited over the network, with no action from the victim.

### Official description

SQL injection vulnerability in dropbase.php in MitriDAT Web Calendar Pro allows remote attackers to modify internal SQL queries and cause a denial of service (inaccessible database) via the tabls parameter.

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

It affects 1 product.


Products: Mitridat Web Calendar Pro.

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

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

## Is CVE-2006-0835 being exploited?

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

Public exploit code:

- Web Calendar Pro - 'Dropbase.php' SQL Injection (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-0835 is a high-severity SQL injection vulnerability in n/a, published on 22 Feb 2006. It can be exploited over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-0835 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-2006-0835/ (Markdown: https://insights.sbomify.com/CVE-2006-0835/index.md)
```

## Sources

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

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