# CVE-2023-47609: SQL injection in OSS Calendar

> Remote authenticated attackers can execute arbitrary code or manipulate database information via SQL injection in OSS Calendar.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 14 Nov 2023
- **Updated:** 8 Jan 2025
- **Also known as:** GHSA-h27g-fv6w-3v3v

## What is CVE-2023-47609?

CVE-2023-47609 is a high-severity SQL injection vulnerability in Thinkingreed Inc. OSS Calendar, published on 14 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SQL injection vulnerability in OSS Calendar versions prior to v.2.0.3 allows a remote authenticated attacker to execute arbitrary code or obtain and/or alter the information stored in the database by sending a specially crafted request.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2023-47609?

It affects 1 product.


Products: Oss-Calendar Oss Calendar.

## How do I fix CVE-2023-47609?

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

## Is CVE-2023-47609 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-47609 and fix it if it is affected.

What it is: CVE-2023-47609 is a high-severity SQL injection vulnerability in Thinkingreed Inc. OSS Calendar, published on 14 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-47609 in the wild and no public exploit code.

Affected product: Thinkingreed Inc. OSS Calendar. 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-2023-47609/ (Markdown: https://insights.sbomify.com/CVE-2023-47609/index.md)
```

## Sources

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

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