CVE-2025-45805
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 · uneditedIn phpgurukul Doctor Appointment Management System 1.0, an authenticated doctor user can inject arbitrary JavaScript code into their profile name. This payload is subsequently rendered without proper sanitization, when a user visits the website and selects the doctor to book an appointment.
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 confidenceThis is a stored Cross-Site Scripting (XSS) vulnerability in phpgurukul Doctor Appointment Management System 1.0. An authenticated doctor user can inject arbitrary JavaScript code into their profile name field, which is then stored in the database. When other users view the doctor's profile to book an appointment, the malicious payload executes in their browser without any sanitization or output encoding.
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
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L
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 the product versionLocate the version information in the system (typically in an about page, footer, or configuration file). Confirm it is version 1.0.0 of phpgurukul Doctor Appointment Management System.Affected if The installed version matches 1.0.0 exactly.
-
Verify doctor user accounts existLog in as a doctor user and navigate to the profile editing section. Look for a field that allows modification of the doctor's name or display name.Affected if Doctor users can access a profile name field that accepts text input.
-
Check profile name rendering in appointment bookingNavigate to the page where patients view doctor profiles to book appointments. View the page source or inspect the HTML element displaying the doctor's name.Affected if The doctor's name is rendered as plain HTML without encoding (e.g., <script> tags appear literally in the source rather than as <script>).
-
Test for output encodingInject a simple test payload like <script>alert('XSS')</script> into the profile name field, save it, then view the page where the name is displayed. Check if the payload executes or is properly escaped.Affected if The script payload executes in the browser or appears unescaped in the HTML source.
-
Inspect application code for sanitizationIf you have access to the source code, search for the PHP files handling profile display. Look for functions like htmlspecialchars, htmlentities, or other encoding functions applied to the doctor's name variable before output.Affected if No output encoding functions are applied to the profile name variable before it is rendered.
You are affected if you are running version 1.0.0 and the doctor's profile name field can be manipulated to contain HTML/JavaScript that executes when other users view the appointment booking page.
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 input validation to reject malicious payloads on input, and apply context-aware output encoding (HTML entity encoding) when rendering the doctor's profile name in all contexts where it is displayed to users.
- 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-2025-45805 — 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-2025-45805 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