# CVE-2026-115247: subhajitkhan online-clinic-management-system patientregistration.php missing encryption


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-8chj-r83q-3m2h

## What is CVE-2026-115247?

CVE-2026-115247 is a medium-severity vulnerability in subhajitkhan online-clinic-management-system, published on 22 Oct 2026. 

### Official description

A security vulnerability has been detected in subhajitkhan online-clinic-management-system up to e9ee77a8827a1446220fa07ee693dc4d9a29a578. This vulnerability affects unknown code of the file patientregistration.php. The manipulation of the argument pat_pswd/doc_pswd leads to missing encryption of sensitive data. It is possible to initiate the attack remotely. The exploit has been disclosed publicly and may be used. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-311 (Missing Encryption of Sensitive Data), CWE-310

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


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

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

## Is CVE-2026-115247 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-115247 is a medium-severity vulnerability in subhajitkhan online-clinic-management-system, published on 22 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-115247 exists.

Affected product: subhajitkhan online-clinic-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-2026-115247/ (Markdown: https://insights.sbomify.com/CVE-2026-115247/index.md)
```

## Sources

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

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