CVE-2026-105175

waiting for further signalsZero needs more public information before it can validate it.

GHSA-rgg9-c68m-whj3 ↗EUVD-2026-92160 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
sourcecodester Drug Recommendation System 1.0
ETK-2026-622, permanent identifier
16d 12h 23msince last run
28mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+3h57m
0
+2h
+6h
+8h
+10h
+12h

description

Drug Recommendation System 1.0 has an SQL injection flaw in its student-registration functionality. A remote, unauthenticated attacker may be able to alter database queries if the affected registration endpoint is reachable.

mitigation

Restrict network access to the student-registration endpoint until the application can be updated or corrected. Use parameterized database queries and server-side input validation for registration fields.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.25%15th percentile
agent run time
28m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-05 00:45Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-05 00:45Z
    ghsa: trigger signal, started the run
  2. 2026-10-05 00:45Z

this entry in the feed

GET /api/v1/feed/CVE-2026-105175

{
  "etk_id": "ETK-2026-622",
  "cve_id": "CVE-2026-105175",
  "display_id": "CVE-2026-105175",
  "ghsa_id": "GHSA-rgg9-c68m-whj3",
  "euvd_id": "EUVD-2026-92160",
  "status": "published",
  "anchor_state": "anchored",
  "title": "SQL injection in Drug Recommendation System registration",
  "summary": "Drug Recommendation System 1.0 has an SQL injection flaw in its student-registration functionality. A remote, unauthenticated attacker may be able to alter database queries if the affected registration endpoint is reachable.",
  "mitigation": "Restrict network access to the student-registration endpoint until the application can be updated or corrected. Use parameterized database queries and server-side input validation for registration fields.",
  "vendor": "sourcecodester",
  "product": "Drug Recommendation System",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "1.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Drug Recommendation System",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L",
  "epss_score": 0.0025,
  "epss_percentile": 0.1591,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 28.094253616666666,
  "t0_at": "2026-10-05T00:45:15.519000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-05T00:45:15.519000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-05T00:45:15.519000+00:00",
      "url": "https://github.com/advisories/GHSA-rgg9-c68m-whj3"
    }
  }
}

published 2026-10-05 04:14Z
last change 2026-10-21 11:52Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.