dbcve.org
Medicine Tracker SystemApplication · Medicine Tracker System Project

CVE-2023-30106

MEDIUM · 6.1 CVSS v3.1 Published 2023-04-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Sourcecodester Medicine Tracker System in PHP 1.0.0 is vulnerable to Cross Site Scripting (XSS) via page=about.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A reflected Cross Site Scripting (XSS) vulnerability exists in the Medicine Tracker System PHP 1.0.0 application. The 'page' parameter on the about page does not properly sanitize user input before reflecting it in the HTML output, allowing an attacker to inject malicious JavaScript that executes in victim browsers.

MitigationImplement proper input validation and output encoding on the page parameter. Use context-appropriate escaping when reflecting any user-controlled data into HTML. Consider implementing a Content Security Policy (CSP) as defense-in-depth.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Medicine Tracker SystemApplication
Affected:= 1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Medicine Tracker System is installed
    Locate the application in the web server document root. Look for directories containing 'medicine' or 'tracker' related PHP files, or check known default paths such as /var/www/html/, /htdocs/, or the web server's configured document root.
    Affected if The Medicine Tracker System PHP application is present on the server.
  2. Verify the application version
    Inspect the application for version information. Check the about page directly at /about.php, or look for version files, README files, or meta tags within the application source code that indicate version 1.0.
    Affected if The installed version is Medicine Tracker System 1.0.
  3. Locate the vulnerable about page
    Access the about page endpoint in the browser or via curl. The vulnerable URL pattern is typically /about.php or a similar path that accepts a 'page' parameter.
    Affected if The about page is accessible and accepts a 'page' parameter.
  4. Test the page parameter for reflected input
    Send a crafted request to the about page with a test payload in the 'page' parameter, such as: /about.php?page=test. Examine the HTML response to see if the value of 'page' appears literally in the response without sanitization or encoding.
    Affected if The 'page' parameter value is reflected directly in the HTML response without being sanitized or encoded.
  5. Confirm the XSS vulnerability exists
    Send a request with an XSS payload like <script>alert(1)</script> in the 'page' parameter and verify it is not filtered or encoded in the response. Check if the raw script tags appear in the HTML output.
    Affected if The 'page' parameter reflects unsanitized user input including HTML or script tags back to the user in the response.

A user is affected if the Medicine Tracker System version 1.0 is installed and the about page reflects the 'page' parameter value directly into HTML without sanitization or encoding, allowing injected JavaScript to execute.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and output encoding on the page parameter. Use context-appropriate escaping when reflecting any user-controlled data into HTML. Consider implementing a Content Security Policy (CSP) as defense-in-depth.

Fix this in Medicine Tracker System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-30106 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-30106 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data