PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-93997 SourceCodester CVE debrief

A weakness has been identified in SourceCodester Drug Recommendation System 1.0. Affected by this issue is some unknown functionality of the file /Admin/edit_symptom.php. This manipulation of the argument ID causes sql injection. The attack is possible to be carried out remotely. The exploit has been made available to the public and could be used for attacks.

Vendor
SourceCodester
Product
Drug Recommendation System
CVSS
MEDIUM 5.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-20
Original CVE updated
2026-09-20
Advisory published
2026-09-20
Advisory updated
2026-09-20

Who should care

Defenders responsible for systems using the SourceCodester Drug Recommendation System 1.0 should assess exposure and prioritize verification and mitigation. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify the presence of this vulnerability in their systems, apply patches or mitigations as available, and monitor for potential attacks.

Why it matters

Defenders should care about CVE-2026-93997 because it is a SQL injection vulnerability in the SourceCodester Drug Recommendation System 1.0 that can be exploited remotely, and the exploit has been made public. This vulnerability requires verification of presence in systems, prioritization of patching or mitigation, and monitoring for potential attacks.

  • Verify potential exposure to SQL injection attacks
  • Assess the risk of remote exploitation
  • Prioritize patching or mitigating the vulnerability
  • Monitor for potential attacks using the public exploit

Technical summary

The vulnerability is caused by a weakness in the /Admin/edit_symptom.php file of the SourceCodester Drug Recommendation System 1.0. The manipulation of the ID argument leads to SQL injection, which can be exploited remotely. This issue affects the confidentiality, integrity, and availability of the system. The exploit has been made public, increasing the risk of attacks. Defenders should prioritize verifying the presence of this vulnerability in their systems and applying patches or mitigations as available. The scope of affected systems and versions is not clearly stated, requiring further verification.

Defensive priority

Defenders should prioritize verifying the presence of this vulnerability in their systems and applying patches or mitigations as available.

Recommended defensive actions

  • Verify the presence of this vulnerability in your systems
  • Apply patches or mitigations as available
  • Monitor for potential attacks
  • Restrict access to the /Admin/edit_symptom.php file
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but the scope of affected systems and versions is not clearly stated. The exploit has been made public, increasing the risk of attacks.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-93997 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-93997

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-93997 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-93997

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.