CVE-2023-6424
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 · uneditedA vulnerability has been discovered in BigProf Online Clinic Management System 2.2, which does not sufficiently encode user-controlled input, resulting in persistent XSS through /clinic/disease_symptoms_view.php, in the FirstRecord parameter. Exploitation of this vulnerability could allow an attacking user to store dangerous JavaScript payloads on the system that will be triggered when the page loads.
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 · high confidenceA stored (persistent) cross-site scripting vulnerability exists in BigProf Online Clinic Management System 2.2 at /clinic/disease_symptoms_view.php via the FirstRecord parameter. User-controlled input is not properly encoded before storage, allowing malicious JavaScript payloads to be persisted and executed in the browsers of other users when they view the affected page.
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= 2.2CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm the application installationLocate BigProf Online Clinic Management System files - typical paths may include /clinic/ or check your web root directory for the application. Look for version identifiers in source files, README, or admin interface.Affected if The application is BigProf Online Clinic Management System version 2.2
-
Verify the vulnerable file existsCheck if /clinic/disease_symptoms_view.php exists in your web server's document root.Affected if The file disease_symptoms_view.php is present in the /clinic/ directory
-
Identify how FirstRecord parameter is handledExamine the disease_symptoms_view.php source code and look for how the FirstRecord parameter is processed, stored in database, and retrieved for display.Affected if The FirstRecord parameter accepts user input and stores it without sanitization or encoding before rendering
-
Check for output encoding in the display codeSearch the codebase for the rendering logic that displays stored FirstRecord values. Look for absence of htmlspecialchars, htmlentities, or similar output encoding functions.Affected if User-supplied data from the FirstRecord parameter is rendered in HTML without proper encoding
You are affected if running BigProf Online Clinic Management System version 2.2 and the FirstRecord parameter in disease_symptoms_view.php stores and displays user input without output encoding.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement robust input validation and context-appropriate output encoding for the FirstRecord parameter and all user-supplied data rendered in disease_symptoms_view.php. Consider deploying a web application firewall as a temporary compensating control.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-6424 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-6424 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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