Skip to main content
VulnerabilityPublished

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

Affects mayurik dawa-pharmaSource CVE Database V5

0

Not known to be exploited · CVSS 8.7 High.

Data as of 26 Oct 2026, 14:05 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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubmayurik/dawa-pharmapkg:github/mayurik/dawa-pharmaOther threatsAffected
  • =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.

References

Community reviews

Loading reviews…