Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure authenticated user to attacker page
-
ExploitDeliver hidden auto-submitting forged form
-
ExecutionBrowser sends request with victim session
-
ImpactUnauthorized state change in application
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V3 - Web Frontend Security Anti-CSRF tokens, SameSite cookies
MITRE ATT&CK
1 technique across 1 tactic: Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an authenticated victim with an active session in the Drug Recommendation System to be lured into visiting attacker-controlled content while logged in (UI:P), because the affected state-changing request lacks anti-CSRF tokens (CWE-352). The attacker needs no credentials of their own (PR:N) and the request travels over the network (AV:N), but success is limited by the need for victim interaction, a valid victim session, and the fact that only limited integrity is affected - no data disclosure or denial of service results. The specific endpoint is not named in the advisory, so defenders must audit all state-changing forms for missing token validation. |
| Impact | This is a low-to-moderate real-world risk despite being remotely reachable. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N) describes an unauthenticated, network-reachable CSRF flaw that requires passive user interaction and yields only limited integrity impact (VI:L) with no confidentiality or availability impact - consistent with the 5.3 medium score. Publicly available exploit code exists (E:P and a GitHub PoC reference), which raises accessibility, but there is no CISA KEV listing and no EPSS score was provided, so there is no evidence of active or widespread exploitation. The dependence on tricking an authenticated victim into visiting a malicious page (UI:P) and the narrow impact mean this is a genuine but not high-priority issue - more relevant for defense-in-depth hardening than emergency patching. Key missing signals: no EPSS probability and no KEV data were supplied, so exploitation likelihood cannot be quantified; treat the PoC as a proof of feasibility, not evidence of in-the-wild use. |
| Exploit ScenarioDerived | An attacker hosts a malicious web page containing a hidden auto-submitting form targeting a state-changing endpoint of the Drug Recommendation System. When an authenticated user (e.g., a logged-in administrator) visits the page, their browser silently submits the forged request using their session, performing an unwanted action without their consent. A public proof-of-concept documenting the missing anti-CSRF tokens is available on GitHub, lowering the barrier to reproduction. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 06, 2026
Cross-site request forgery in SourceCodester Drug Recommendation System 1.0 allows a remote attacker to make an authenticated victim's browser submit unintended state-changing requests, because the application's forms do not validate anti-CSRF tokens (CWE-352). The attacker needs no credentials of their own (CVSS:3.1 AV:N/AC:L/PR:N/UI:R/S:U), but success requires luring a logged-in victim to attacker-controlled content while their session is active, and the resulting impact is limited to low integrity with no confidentiality or availability loss. Publicly available exploit code exists (published in the hackliu/Vulnerability-Reports repository as VULN-06-CSRF-Missing-Tokens.md), but there is no evidence of confirmed active exploitation (not listed in CISA KEV), so this should be treated as a low-to-moderate real-world risk rather than a mass-exploitation event.
RemediationAI
No vendor-released patch was identified at time of analysis, and the SourceCodester distribution model (project source packages) means a fixed build should not be assumed; treat the vendor site and the VulDB entry (https://vuldb.com/vuln/413699) as the places to watch for an updated release. Until one appears, the effective remediations are application-side: add and validate per-session anti-CSRF tokens on every state-changing form and AJAX call, and use framework-level CSRF middleware if one is available; set session cookies with SameSite=Lax or Strict (Strict is stronger but can break legitimate cross-site navigation and SSO-style flows) and mark them HttpOnly/Secure; require re-authentication or a password/confirmation step for high-impact actions so a forged request alone is insufficient. Because the vulnerable endpoints are not enumerated in the advisory, defenders should audit all POST/PUT/DELETE handlers in the 1.0 codebase, adding Origin/Referer validation as a secondary check (bypassable in some client configurations, so never a sole control). Administratively, restrict the application to trusted networks or a VPN and remove it from direct internet exposure where it is only used for evaluation, and deploy WAF rules that block cross-origin state-changing requests; these compensating controls reduce exposure but do not remove the underlying missing-token flaw, and the network restrictions will impede legitimate remote users.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-352 (Cross-Site Request Forgery): the affected state-changing functionality in Drug Recommendation System 1.0 performs actions based solely on the browser-supplied session cookie without requiring a per-request, unpredictable token tied to the user's session. Because browsers automatically attach cookies to any request originating from a page the victim is visiting, an attacker-controlled page, image tag, or auto-submitted form can silently trigger privileged operations in the context of the victim's authenticated session. The CVSS 4.0 vector supplied by the source (AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/E:P) and our independent CVSS 3.1 assessment (AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N) agree on the essentials: network-reachable, no attacker authentication, victim interaction required, and a purely low-integrity outcome with no data disclosure or denial of service. The CPE entry cpe:2.3:a:sourcecodester:drug_recommendation_system:* indicates the vendor/application pair with an unbounded version range, and the advisory does not name the specific endpoint or parameter, so the vulnerable surface must be inferred by auditing every state-changing request. Note the scoring-scale discrepancy between the reported CVSS 4.0 score (5.3) and the 3.x-equivalent assessment, which put the practical severity in the low-to-moderate band.
Know when Drug Recommendation System gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P
Remote token-less CSRF needing a logged-in victim to trigger the request, so AV:N/PR:N/UI:R with only limited integrity impact and no confidentiality or availability effect.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
Lifecycle Timeline
3DescriptionCVE.org
A weakness has been identified in SourceCodester Drug Recommendation System 1.0. Affected is an unknown function. Executing a manipulation can lead to cross-site request forgery. The attack may be performed from remote. The exploit has been made available to the public and could be used for attacks.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Request Forgery exploits the automatic credential inclusion behavior of web browsers.
More in Drug Recommendation System
View allAuthentication bypass in SourceCodester Drug Recommendation System 1.0 lets remote, unauthenticated attackers impersonat
SQL injection in SourceCodester Drug Recommendation System 1.0 lets a remote attacker manipulate the SQL query behind /d
SQL injection in SourceCodester Drug Recommendation System 1.0 allows remote attackers to manipulate the ID parameter in
Cross-site scripting in SourceCodester Drug Recommendation System 1.0 allows unauthenticated remote attackers to inject
Cross-site scripting (XSS) in SourceCodester Drug Recommendation System 1.0 allows remote attackers to inject malicious
Stored cross-site scripting in SourceCodester Drug Recommendation System 1.0 allows an authenticated user with access to
Stored cross-site scripting in the admin symptom-management form (drug_recommender/Admin/add_symptom) of SourceCodester
SQL injection in SourceCodester Drug Recommendation System 1.0 allows unauthenticated remote attackers to execute arbitr
Cross-site scripting in SourceCodester Drug Recommendation System 1.0 allows remote, unauthenticated attackers to inject
Stored cross-site scripting in SourceCodester Drug Recommendation System 1.0 lets unauthenticated remote attackers injec
SQL injection in SourceCodester Drug Recommendation System 1.0 allows an authenticated administrator to inject arbitrary
SQL injection in the admin Drug Creation routine of SourceCodester Drug Recommendation System 1.0 lets an attacker with
EUVD-2026-92947
GHSA-g459-jpwv-h5m2
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB