# CVE-2026-61294: SQL injection in Oracle Common Applications Calendar

> A low-privileged attacker can exploit SQL injection in Oracle Common Applications Calendar to read, modify, or delete data and cause partial denial of service.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **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:** 21 Jul 2026
- **Updated:** 22 Jul 2026
- **Also known as:** GHSA-vf52-q35r-885q

## What is CVE-2026-61294?

CVE-2026-61294 is a medium-severity SQL injection vulnerability in Oracle Common Applications Calendar, published on 21 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Vulnerability in the Oracle Common Applications Calendar product of Oracle E-Business Suite (component: Calendar Synchronizations).  Supported versions that are affected are 12.2.3-12.2.15. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Common Applications Calendar.  Successful attacks of this vulnerability can result in  unauthorized update, insert or delete access to some of Oracle Common Applications Calendar accessible data as well as  unauthorized read access to a subset of Oracle Common Applications Calendar accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Common Applications Calendar. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L).

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-284 (Improper Access Control), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-61294?

It affects 1 product.


Products: Oracle Common Applications Calendar.

## How do I fix CVE-2026-61294?

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

## Is CVE-2026-61294 being exploited?

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

## Other vulnerabilities in Oracle Common Applications Calendar

- [CVE-2016-3541](https://insights.sbomify.com/CVE-2016-3541/): Information disclosure in n/a (critical 9.1)
- [CVE-2016-3543](https://insights.sbomify.com/CVE-2016-3543/): Information disclosure in n/a (critical 9.1)
- [CVE-2021-2034](https://insights.sbomify.com/CVE-2021-2034/): Information disclosure in Common Applications Calendar (high 8.2)
- [CVE-2021-2114](https://insights.sbomify.com/CVE-2021-2114/): Cross-site scripting in Common Applications Calendar (high 8.2)
- [CVE-2020-2820](https://insights.sbomify.com/CVE-2020-2820/): Cross-site scripting in Common Applications Calendar (high 8.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-61294 and fix it if it is affected.

What it is: CVE-2026-61294 is a medium-severity SQL injection vulnerability in Oracle Common Applications Calendar, published on 21 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-61294 in the wild and no public exploit code.

Affected product: Oracle Common Applications 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-2026-61294/ (Markdown: https://insights.sbomify.com/CVE-2026-61294/index.md)
```

## Sources

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

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