CVE-2022-31497
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 · uneditedLibreHealth EHR Base 2.0.0 allows interface/main/finder/finder_navigation.php patient XSS.
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 confidenceLibreHealth EHR Base 2.0.0 contains a reflected cross-site scripting (XSS) vulnerability in interface/main/finder/finder_navigation.php where patient-related data is rendered without proper input sanitization or output encoding, allowing attackers to inject malicious JavaScript through patient parameters.
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.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.
-
Confirm LibreHealth EHR installation and versionLocate the LibreHealth EHR installation directory and identify the installed version number. Check version files, about pages, or administrative interfaces that display the software version.Affected if The installed version is LibreHealth EHR Base 2.0.0
-
Verify finder_navigation.php existsLocate the file finder_navigation.php within the interface/main/finder/ directory of the LibreHealth EHR installation.Affected if The file finder_navigation.php exists at interface/main/finder/ in the LibreHealth EHR web root
-
Inspect patient parameter handling in finder_navigation.phpOpen finder_navigation.php and examine how patient-related parameters (such as patient ID, name, or other patient data) are processed and rendered. Look for code that outputs these parameters directly to HTML without sanitization functions like htmlspecialchars() or equivalent output encoding.Affected if The file contains code that renders patient parameters directly to HTML output without proper output encoding or input sanitization
-
Test for XSS vulnerability via URL parameter injectionIf the application is running, craft a request to finder_navigation.php with a malicious JavaScript payload in a patient-related parameter (e.g., ?patient=<script>alert('XSS')</script>) and observe if the script executes in the response.Affected if The application reflects the injected payload in the response without encoding or filtering
You are affected if LibreHealth EHR Base 2.0.0 is installed and finder_navigation.php renders patient-related parameters without output encoding, allowing arbitrary JavaScript injection through URL parameters.
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 dataApply context-appropriate output encoding/escaping when rendering patient data in finder_navigation.php and implement input validation for all patient-related parameters to prevent XSS injection.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-31497 — 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-31497 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