CVE-2023-53734VulnerabilityPublished 4 Dec 2025

CVE-2023-53734: mayurik dawa-pharma · SQL Injection

Affects mayurik dawa-pharmaSource CVE Database V5

Not known to be exploited · CVSS 8.7 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

8.7High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: High
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubmayurik/dawa-pharma`pkg:github/mayurik/dawa-pharma`Other threats	Affected =1.0-2022	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediately restrict network access to the dawa-pharma application to trusted internal users until a patch is available. 2. Implement Web Application Firewalls (WAF) with custom rules to detect and block SQL injection patterns targeting the application. 3. Conduct a thorough code review and refactor the application to use parameterized queries or prepared statements to eliminate SQL injection vectors. 4. Enforce strict input validation and sanitization on all user-supplied data before processing. 5. Limit database user privileges to the minimum necessary, preventing administrative-level access from the application layer. 6. Monitor database logs and application logs for unusual query patterns or access attempts indicative of exploitation attempts. 7. Develop and deploy patches as soon as the vendor releases them, and test thoroughly before production deployment. 8. Educate developers and IT staff on secure coding practices to prevent similar vulnerabilities in future releases.

Description

dawa-pharma-1.0 allows unauthenticated attackers to execute SQL queries on the server, allowing them to access sensitive information and potentially gain administrative access.

Impact

For European organizations, especially those in the healthcare and pharmaceutical sectors, this vulnerability could lead to severe data breaches involving sensitive patient and drug information. Unauthorized access to such data can result in regulatory penalties under GDPR, loss of patient trust, and potential disruption of healthcare services. The ability to gain administrative access could allow attackers to manipulate or delete critical data, disrupt operations, or use the compromised system as a foothold for further attacks within the network. Given the critical infrastructure role of healthcare and pharmaceutical industries in Europe, exploitation could have cascading effects on public health and safety. Additionally, the exposure of intellectual property related to pharmaceuticals could have economic repercussions. The vulnerability's ease of exploitation without authentication increases the likelihood of attacks, making it a pressing concern for European entities using dawa-pharma 1.0.

Summary

CVE-2023-53734 is a critical SQL Injection vulnerability identified in version 1.0 of the dawa-pharma application developed by mayurik. The flaw stems from improper neutralization of special characters in SQL commands (CWE-89), allowing unauthenticated attackers to inject malicious SQL queries directly into the backend database. This vulnerability requires no authentication or user interaction, making it trivially exploitable remotely over the network. Successful exploitation can lead to unauthorized disclosure of sensitive information stored in the database, such as patient records or pharmaceutical data, and may allow attackers to escalate privileges to administrative levels within the application. The CVSS 4.0 score of 8.7 reflects the high impact on confidentiality and the ease of exploitation. No patches or fixes have been published yet, and no known exploits are currently reported in the wild. The vulnerability affects the 1.0-2022 release of dawa-pharma, a software likely used in pharmaceutical or healthcare contexts. Given the critical nature of the data handled by such applications, this vulnerability poses a significant risk to data integrity and privacy. The lack of authentication requirements and the ability to execute arbitrary SQL commands make this a severe threat that demands immediate attention from affected organizations.

CWE-89Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #2OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Parameterization
If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.
Architecture and Design · Operation · Environment Hardening
Run your code using the lowest privileges that are required to accomplish the necessary tasks. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment.
OWASP Cheat Sheets
Query Parameterization (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
XML Security (opens in a new tab)
XML External Entity Prevention (opens in a new tab)
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.4 (opens in a new tab)
V5.3.5 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
Command Line Execution through SQL Injection (opens in a new tab)
Object Relational Mapping Injection (opens in a new tab)
SQL Injection through SOAP Parameter Tampering (opens in a new tab)
Expanding Control over the Operating System from the Database (opens in a new tab)
SQL Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Dec 2025, 22:10 UTC

WeaknessesCWE-89

Technical details

References

Community reviews

Related threats