What is CVE-2026-105179?

CVE-2026-105179 is SourceCodester Drug Recommendation System Password add_user.php missing encryption. The supplied enrichment data classifies it as Unclassified mapped to CWE-311 CWE-311; CWE-310 CWE-310.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Active exploitation is not confirmed from current sources for CVE-2026-105179. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2026-105179 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

A public PoC is not confirmed from current sources for CVE-2026-105179. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-105179 using CVSS 2.7, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

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. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

low

CVE-2026-105179

CVE-2026-105179 — SourceCodester Drug Recommendation System Password add_user.php missing encryption

A weakness has been identified in SourceCodester Drug Recommendation System 1.0. This affects an unknown function of the file Admin/add_user.php of the component Password Handler. Executing a manipulation of the argument Password can lead to missing encryption of sensitive data. It is possible to launch the attack remotely. The exploit has been made available to the public and could be used for attacks.

Published Oct 5, 2026Updated Oct 5, 2026Sources: 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

ahead of 0% of scored CVEs

Affects

SourceCodester

Drug Recommendation System

CVSS base

2.7

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.

Vendor	Product	Versions	Status
SourceCodester	Drug Recommendation System	1.0	Vulnerable

Attack characteristics

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

Availability

None

Confidentiality

Low

Integrity

None

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

High

User Interaction

None

Every base score collected

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

Score	Version	Severity	Expl.	Impact	Source
2.7	CVSS 3.1	low	1.2	1.4	NVD, GHSA
3.3	CVSS 2.0	low	6.4	2.9	vuldb.com (CNA)
5.1	CVSS 4.0	medium	—	—	SourceCodester (CNA)
2.7	CVSS 3.1	low	—	—	SourceCodester (CNA)
2.7	CVSS 3.0	low	—	—	SourceCodester (CNA)
3.3	CVSS 2.0	low	—	—	SourceCodester (CNA)

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/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-311 · Missing Encryption of Sensitive Data

Read Application Data
Modify Application Data

Mitigation: Clearly specify which data or resources are valuable enough that they should be protected by encryption. Require that any transmission or storage of this data/resource should use well-vetted encryption algorithms.

Weakness & attack patterns

CWE-311
CWE-310

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

CAPEC-485 · Signature Spoofing by Key Recreation

T1040Network Sniffing
T1111Multi-Factor Authentication Interception
T1005Data from Local System

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 /add_user.php.
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.

2026
Added · CVSS 3.1 2.7 (AV:N)
Oct 5, 2026 · NVD
Initial · CVE published
Oct 5, 2026 · NVD
Added · GHSA-xc22-rxmg-hqj7 published (low)
Oct 5, 2026 · GitHub Security Advisory
CVE published by NIST.
Oct 5, 2026 · SOCRadar CTI
Reported · Advisory disclosed
Oct 4, 2026 · SourceCodester
Reported · VulDB entry created
Oct 4, 2026 · SourceCodester
Reported · VulDB entry last update
Oct 4, 2026 · SourceCodester

Source activity

Readings a source repeats on a schedule, counted rather than listed.

2×ModifiedOct 5, 2026 · SOCRadar CTI

References

7 on the record

vuldb.com/cve/CVE-2026-105179
Vendor Advisory
vuldb.com/submit/970935
Vendor Advisory
vuldb.com/vuln/413411
Vendor Advisory
vuldb.com/vuln/413411/cti
Vendor Advisory
www.sourcecodester.com/
Vendor Advisory, NIST
nvd.nist.gov/vuln/detail/CVE-2026-105179
NVD
github.com/advisories/GHSA-xc22-rxmg-hqj7
Exploit, Third Party Advisory

Coverage

1 story from the feeds we poll

CVE-2026-105179
vuldb.com · Oct 4, 2026

Elsewhere on this site

SourceCodesterevery CVE for this vendor
Unclassifiedsame class
CWE-311other pages naming this weakness

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-105179 is SourceCodester Drug Recommendation System Password add_user.php missing encryption, 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-105179. Public exploit evidence is: A public PoC is not confirmed from current sources for CVE-2026-105179. 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 2.7 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.