Doctor-Appointment-System remote SQL injection in login component
- Exploited
- Proof of concept public, per CISA
- Fix
- No fix listed
- Who is exposed
- Not reported
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
Original 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 systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
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"}.Affected versions
- rajesh2211 Doctor-Appointment-SystemVersion range not reported
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.9/10CVSS 6.9
- No patch5/5No patch listed yet
What would change the score
- Would score about 77 if added to CISA KEV
- Would score about 72 if CISA's SSVC rates exploitation active
- Would score about 52 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: yes · Technical impact: partial
- Record last updated
Evidence 7
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133478 |
| Record | NVD · CVE-2026-133478 |
| Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | GitHub · To-LingJing/CVE-Issues · Issue #9 |
| Other links 4 | |
| Advisory | VulDB · Advisory #440880 |
| Advisory | VulDB · Threat intelligence #440880 |
| Advisory | VulDB · CVE-2026-133478 record |
| Advisory | VulDB · Submission #1048484 |
Related
- CVE-2026-129175U.S Department of the Interior Unstable Slope Management Program unauthenticated SQL Injection
- CVE-2026-87977IBM Guardium Data Protection SQL Injection
- CVE-2026-129043WordPress Newsletters plugin <= 4.18.2 - SQL Injection vulnerability
- CVE-2026-133534Neotroni Lighting|PowerLink - SQL Injection
- CVE-2026-128915WordPress InstaWP Connect plugin <= 0.1.4.4 - SQL Injection vulnerability
- CVE-2026-122676WordPress PublishPress Authors plugin <= 4.18.0 - SQL Injection vulnerability
No corrections so far. Something wrong on this page? Report an error.