CVE Intelligence
Analysis AI-assisted

CVE-2026-2057: SQL Injection in SourceCodester Medical Center Portal Management System 1.0 login

CVE-2026-2057 is an SQL injection weakness (CWE-89) in the /login.php page of Medical Center Portal Management System 1.0, a product attributed to SourceCodester in the record. The record states it can be triggered remotely and that a public exploit exists, but CISA KEV does not list it and no confirmed exploitation in the wild appears in the sources consulted. No vendor fix is recorded, so defenders should treat the product as exposed until the vendor or maintainers confirm otherwise.

Published Oct 13, 2026 · Updated Oct 13, 2026 · Ler em português

Overview

CVE-2026-2057 describes an SQL injection weakness (CWE-89) affecting the /login.php file of Medical Center Portal Management System 1.0, distributed in the record under SourceCodester. The description says the manipulation of the User argument leads to SQL injection, that the attack can be carried out remotely, and that a public exploit is available.

Impact

SQL injection flaws can let an attacker influence database queries built by the application, which may expose, alter or disrupt stored data. The NVD assessment (CVSS 3.1, score 9.8) rates confidentiality, integrity and availability impacts as high, with network attack vector, low complexity, no privileges and no user interaction required. Other CNA scores in the record are lower, so the real-world severity depends on the deployment.

Affected products and versions

  • The record lists version 1.0 of the Medical Center Portal Management System.
  • The product vendor is inconsistent in the record: the description names SourceCodester, while the affected product field names Bontrofftech. The correct vendor is not confirmed.
  • No fixed version is listed.

Exploitation status

The record says an exploit is public and may be used, and a GitHub issue in the references is tagged as an exploit source. CISA KEV does not list this CVE, and no confirmed active exploitation in the wild appears in the sources consulted.

Remediation and mitigation

  • No vendor patch is recorded. Confirm with SourceCodester or the software maintainers whether a fix exists before assuming one does.
  • Restrict access to the login interface, for example through network segmentation, VPN-only access or allowlisting, while the product is evaluated.
  • Ask developers to replace dynamically built SQL in authentication code with parameterized queries or prepared statements, and to validate input on the server side.
  • If the application is not needed, remove or isolate it. Keep an inventory so that copies of this application in the environment are found.
  • Consider a web application firewall as a temporary compensating control, understanding that it does not replace a code fix.

Detection guidance

  • Review web server and application logs for /login.php requests with unusual parameter content, repeated failed logins, or database error messages returned to clients.
  • Monitor database logs for authentication queries with unexpected structure or volume.
  • Alert on successful logins from unexpected sources or accounts shortly after suspicious login activity.

Limitations of the available information

  • No fixed version, vendor advisory or patch is included in the record.
  • The vendor name is inconsistent between the description and the affected product field.
  • CVSS scores differ by provider: NVD gives 9.8 (CVSS 3.1), while the CNA gives 5.5 (CVSS 4.0), 7.3 (CVSS 3.1) and 7.5 (CVSS 2.0). The CNA scores are reported as they appear in the record.
  • No EPSS or SSVC data is available.
  • The record does not include a title, so the title shown here is derived from the description.

Frequently asked questions

Is CVE-2026-2057 being actively exploited?

CISA KEV does not list this CVE, and no confirmed exploitation in the wild appears in the sources consulted. The record does say a public exploit exists and may be used.

Is there a fix for CVE-2026-2057?

No fixed version or vendor patch is listed in the record. Confirm with the vendor or maintainers before assuming a fix exists.

What is the severity of CVE-2026-2057?

NVD assigns a CVSS 3.1 score of 9.8. The CNA scores in the record are lower (5.5 under CVSS 4.0, 7.3 under CVSS 3.1 and 7.5 under CVSS 2.0), so severity varies by provider.

What should defenders do now?

Restrict access to the login interface, check whether the application is needed, look for parameterized query support in the code, and monitor logs for suspicious login activity.

This analysis was drafted with AI assistance from verified source data and automatically checked against it.