CVE-2022-46128
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 · uneditedphpgurukul Doctor Appointment Management System V 1.0.0 is vulnerable to Cross Site Scripting (XSS) via searchdata=.
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 confidenceThe Doctor Appointment Management System 1.0.0 fails to properly sanitize user input in the searchdata parameter, allowing injection of malicious JavaScript that executes in the context of other users' browsers. This is a reflected XSS vulnerability where unsanitized input is immediately reflected back in the application response.
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= 1.0.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed versionLocate the version file or header in the Doctor Appointment Management System installation directory. Common paths include a version.php file, README, or check the admin dashboard for version information.Affected if The installed version is exactly 1.0.0
-
Locate the searchdata parameter handlerSearch the application source code for files handling the searchdata parameter. Look in PHP files within the application root, typically in the patient-facing or search functionality areas.Affected if The searchdata parameter is processed and reflected in the response without visible sanitization logic
-
Test for reflected inputSubmit a harmless test string such as <script>alert(1)</script> or a benign alternative like <img src=x onerror=alert(1)> in the searchdata parameter via a GET or POST request to the search functionality.Affected if The submitted test string appears literally in the HTML response without being escaped or encoded
-
Verify context of reflectionInspect the HTTP response when the searchdata parameter is submitted. Check if the input appears within HTML tags, attributes, or JavaScript contexts without proper encoding.Affected if The input is reflected directly into the HTML output without context-aware encoding
A user is affected if they are running Doctor Appointment Management System version 1.0.0 and the application reflects unsanitized searchdata parameter input in its response.
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 proper input validation and output encoding for all user-supplied data, specifically sanitizing the searchdata parameter before reflecting it in HTML. Use context-appropriate encoding and consider implementing a Content Security Policy (CSP) as a defense-in-depth measure.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46128 — 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-2022-46128 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