CVE Intelligence
Skip to main content
lowCross-site Scripting

CVE-2026-94033

CVE-2026-94033 — SourceCodester Drug Recommendation System User Management add_user cross site scripting

A vulnerability has been found in SourceCodester Drug Recommendation System 1.0. This vulnerability affects unknown code of the file /drug_recommender/Admin/add_user of the component User Management. Such manipulation of the argument txtname/txtemail/txtpassword leads to cross site scripting. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.

Published Updated Sources: NVD, SourceCodester (CNA), GitHub, GitHub Security Advisory, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

0%

ahead of 0% of scored CVEs

Affects

SourceCodester

Drug Recommendation System

CVSS base

3.5

low · 6 sources

Remediation

The vendor's own words where we have them.

Upgrade Drug Recommendation System to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

  • Identify exposed assets running affected vendor/product/version combinations.
  • Prioritize based on EPSS, PoC availability, and external exposure.
  • Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

VendorProductVersionsStatus
SourceCodesterDrug Recommendation System1.0Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

None

Confidentiality

None

Integrity

Low

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

Low

User Interaction

Required

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
3.5CVSS 3.1low2.11.4NVD, GHSA
4CVSS 2.0medium82.9vuldb.com (CNA)
5.1CVSS 4.0medium——SourceCodester (CNA)
3.5CVSS 3.1low——SourceCodester (CNA)
3.5CVSS 3.0low——SourceCodester (CNA)
4CVSS 2.0medium——SourceCodester (CNA)

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-94 · Improper Control of Generation of Code ('Code Injection')

  • Bypass Protection Mechanism
  • Gain Privileges or Assume Identity
  • Execute Unauthorized Code or Commands
  • Hide Activities

Mitigation: Refactor your program so that you do not have to dynamically generate code.

CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

  • Bypass Protection Mechanism
  • Read Application Data
  • Execute Unauthorized Code or Commands

Mitigation: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples of libraries and frameworks that make it easier to generate properly encoded output include Microsoft's Anti-XSS library, the OWASP ESAPI Encoding module, and Apache Wicket.

Weakness & attack patterns

  • CWE-79Cross-site Scripting
  • CWE-94Code Injection

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-85 · AJAX FingerprintingCAPEC-591 · Reflected XSSCAPEC-63 · Cross-Site Scripting (XSS)CAPEC-209 · XSS Using MIME Type MismatchCAPEC-592 · Stored XSSCAPEC-588 · DOM-Based XSS
  • T1027.006Obfuscated Files or Information: HTML Smuggling
  • T1027.009Obfuscated Files or Information: Embedded Payloads
  • T1564.009Hide Artifacts: Resource Forking

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

  • Search application, proxy, and WAF logs for requests touching /drug_recommender/Admin/add_user, /txtemail/txtpassword.
  • Prioritize edge telemetry for network-reachable Drug Recommendation System.
web/proxy/WAF logsapplication logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

  1. 2026
  2. Added · CVSS 3.1 3.5 (AV:N)

    Sep 20, 2026 · NVD

  3. Initial · CVE published

    Sep 20, 2026 · NVD

  4. Added · GHSA-p798-gw99-hgcp published (low)

    Sep 20, 2026 · GitHub Security Advisory

  5. CVE published by MITRE.

    Sep 20, 2026 · SOCRadar CTI

  6. Reported · Advisory disclosed

    Sep 19, 2026 · SourceCodester

  7. Reported · VulDB entry created

    Sep 19, 2026 · SourceCodester

  8. Reported · VulDB entry last update

    Sep 19, 2026 · SourceCodester

References

8 on the record

Coverage

1 story from the feeds we poll

Elsewhere on this site

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1

What should defenders know first?

CVE-2026-94033 is SourceCodester Drug Recommendation System User Management add_user cross site scripting, a low vulnerability affecting Drug Recommendation System from SourceCodester. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-94033. Public exploit evidence is: A public PoC is not confirmed from current sources for CVE-2026-94033. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 3.5 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.