# CVE-2013-10019: OCLC-Research OAICat sql injection


- **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
- **Fix available:** No
- **Published:** 20 Feb 2023
- **Updated:** 12 Mar 2025
- **Also known as:** GHSA-2652-m543-h3h5

## What is CVE-2013-10019?

CVE-2013-10019 is a medium-severity vulnerability in OCLC-Research OAICat, published on 20 Feb 2023. 

### Official description

A vulnerability was found in OCLC-Research OAICat 1.5.61. It has been rated as critical. This issue affects some unknown processing. The manipulation leads to sql injection. The attack may be initiated remotely. Upgrading to version 1.5.62 is able to address this issue. The identifier of the patch is 6cc65501869fa663bcd24a70b63f41f5cfe6b3e1. It is recommended to upgrade the affected component. The identifier VDB-221489 was assigned to this vulnerability.

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

## Which versions are affected by CVE-2013-10019?

It affects 1 product.


Products: Oclc Oaicat.

## How do I fix CVE-2013-10019?

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

## Is CVE-2013-10019 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-10019 and fix it if it is affected.

What it is: CVE-2013-10019 is a medium-severity vulnerability in OCLC-Research OAICat, published on 20 Feb 2023. 
Exploitation: There is no known exploitation of CVE-2013-10019 in the wild and no public exploit code.

Affected product: OCLC-Research OAICat. 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-2013-10019/ (Markdown: https://insights.sbomify.com/CVE-2013-10019/index.md)
```

## Sources

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

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