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

> Remote attackers can execute arbitrary SQL commands via the Admin_id field in Ocean12 Calendar manager, potentially compromising data integrity and confidentiality.

- **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:** Not needed
- **Fix available:** No
- **Published:** 22 Apr 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-hj63-xjxh-c63g

## What is CVE-2005-1223?

CVE-2005-1223 is a high-severity SQL injection vulnerability in n/a, published on 22 Apr 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in Ocean12 Calendar manager 1.01 allow remote attackers to execute arbitrary SQL commands via the Admin_id field.

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

It affects 1 product.


Products: Ocean12 Technologies Calendar Manager Pro.

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

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

## Is CVE-2005-1223 being exploited?

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

Public exploit code:

- Ocean12 Calendar Manager 1.0 - Admin Form SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2005-4657](https://insights.sbomify.com/CVE-2005-4657/): Auth bypass in n/a (high 7.5)
- [CVE-2006-2264](https://insights.sbomify.com/CVE-2006-2264/): SQL injection in n/a (medium 6.5)
- [CVE-2006-2265](https://insights.sbomify.com/CVE-2006-2265/): Cross-site scripting in n/a (low 2.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-1223 is a high-severity SQL injection vulnerability in n/a, published on 22 Apr 2005. Any signed-in user can exploit it 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-2005-1223 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-2005-1223/ (Markdown: https://insights.sbomify.com/CVE-2005-1223/index.md)
```

## Sources

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

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