# CVE-2025-3243: code-projects Patient Record Management System dental_form.php sql injection

> Remote attackers can exploit SQL injection in dental_form.php to read or modify patient records in the Patient Record Management System.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **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:** 4 Apr 2025
- **Updated:** 1 May 2025
- **Also known as:** GHSA-jprx-q4jj-hvwc

## What is CVE-2025-3243?

CVE-2025-3243 is a medium-severity SQL injection vulnerability in code-projects Patient Record Management System, published on 4 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in code-projects Patient Record Management System 1.0 and classified as critical. This issue affects some unknown processing of the file /dental_form.php. The manipulation of the argument itr_no/dental_no leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2025-3243?

It affects 1 product.


Products: Code-Projects Patient Record Management System.

## How do I fix CVE-2025-3243?

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

## Is CVE-2025-3243 being exploited?

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

Public exploit code:

- A proof-of-concept exploit for CVE-2025-32433, a critical vulnerability in Erlang's SSH library that allows pre-authenticated code execution via malformed SSH_MSG_CHANNEL_REQUEST packets. (github_poc): https://github.com/TeneBrae93/CVE-2025-3243

## Other vulnerabilities in code-projects Patient Record Management System

- [CVE-2024-9034](https://insights.sbomify.com/CVE-2024-9034/): code-projects Patient Record Management System login.php sql injection (medium 6.9)
- [CVE-2026-2706](https://insights.sbomify.com/CVE-2026-2706/): code-projects Patient Record Management System fecalysis_not.php sql injection (medium 5.3)
- [CVE-2025-5762](https://insights.sbomify.com/CVE-2025-5762/): code-projects Patient Record Management System view_hematology.php sql injection (medium 5.3)
- [CVE-2025-5779](https://insights.sbomify.com/CVE-2025-5779/): code-projects Patient Record Management System birthing.php sql injection (medium 5.3)
- [CVE-2025-5780](https://insights.sbomify.com/CVE-2025-5780/): code-projects Patient Record Management System view_dental.php sql injection (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3243 and fix it if it is affected.

What it is: CVE-2025-3243 is a medium-severity SQL injection vulnerability in code-projects Patient Record Management System, published on 4 Apr 2025. 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-2025-3243 exists.

Affected product: code-projects Patient Record Management System. 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-2025-3243/ (Markdown: https://insights.sbomify.com/CVE-2025-3243/index.md)
```

## Sources

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

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