# CVE-2023-33481: RemoteClinic 2.0 is vulnerable to a time-based blind SQL injection attack in the 'start' GET parameter of patients/index.php.


- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 7 Nov 2023
- **Updated:** 5 Sep 2024
- **Also known as:** GHSA-55jv-g63w-9jph

## What is CVE-2023-33481?

CVE-2023-33481 is a critical vulnerability in n/a, published on 7 Nov 2023. 

### Official description

RemoteClinic 2.0 is vulnerable to a time-based blind SQL injection attack in the 'start' GET parameter of patients/index.php.

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

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

It affects 1 product.


Products: Remoteclinic Remote Clinic.

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

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

## Is CVE-2023-33481 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-33478](https://insights.sbomify.com/CVE-2023-33478/): SQL injection in n/a (critical 9.8)
- [CVE-2023-33479](https://insights.sbomify.com/CVE-2023-33479/): SQL injection in n/a (critical 9.8)
- [CVE-2022-48152](https://insights.sbomify.com/CVE-2022-48152/): SQL injection in n/a (critical 9.8)
- [CVE-2023-33480](https://insights.sbomify.com/CVE-2023-33480/): File upload in n/a (high 8.8)
- [CVE-2025-9772](https://insights.sbomify.com/CVE-2025-9772/): RemoteClinic edit.php unrestricted upload (medium 6.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-33481 is a critical vulnerability in n/a, published on 7 Nov 2023. 
Exploitation: There is no known exploitation of CVE-2023-33481 in the wild and no public exploit code.

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-2023-33481/ (Markdown: https://insights.sbomify.com/CVE-2023-33481/index.md)
```

## Sources

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

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