CVE-2023-4495
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 · uneditedEasy Chat Server, in its 3.1 version and before, does not sufficiently encrypt user-controlled inputs, resulting in a Cross-Site Scripting (XSS) vulnerability stored via /registresult.htm (POST method), in the Resume parameter. The XSS is loaded from /register.ghp.
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 confidenceEasy Chat Server 3.1 and prior versions contain a stored Cross-Site Scripting (XSS) vulnerability in the Resume parameter of the /registresult.htm endpoint (POST method). User-supplied input in the Resume field is not properly sanitized before storage, allowing malicious JavaScript to be persisted and loaded when users access /register.ghp.
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<= 3.1CVSS 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 Easy Chat Server installationLocate the Easy Chat Server installation directory, typically found in C:\Program Files\Easy Chat Server or C:\Program Files (x86)\Easy Chat Server. Check for the executable or check Windows Programs and Features for the installed application.Affected if Easy Chat Server version 3.1 or lower is installed
-
Identify the server versionCheck the application's About section, the executable file properties (right-click on the main .exe file and view Version tab), or look for a version.txt or readme.txt file in the installation directory.Affected if The installed version is 3.1 or any version prior to 3.1
-
Verify the vulnerable endpoint existsLocate the web root directory of the Easy Chat Server installation. Check for the presence of registresult.htm and register.ghp files in the web directory (typically in a /www or /htdocs subfolder).Affected if These files exist and the server is configured to handle POST requests to /registresult.htm
-
Inspect Resume field handling in the applicationExamine the server-side code that processes the /registresult.htm endpoint. Look for how the Resume parameter is handled in the registration process. Check if the application stores user input from the Resume field without sanitization.Affected if The Resume parameter from POST requests is stored directly without input validation or output encoding
-
Check for stored malicious scriptsReview the application's data storage (database or flat file) where user profile information is stored. Look for any entries in the Resume field that contain script tags, javascript:, or other XSS payloads.Affected if JavaScript code is stored in Resume field entries and can be loaded when accessing /register.ghp
A user is affected if Easy Chat Server version 3.1 or lower is installed and the Resume parameter in the registration process does not sanitize user input before storing it, allowing stored XSS to be executed when /register.ghp is accessed.
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 server-side input validation and output encoding for the Resume parameter to sanitize user-controlled data before storage and display. Additionally, configure Content Security Policy (CSP) headers to help prevent XSS execution.
- 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-4495 — 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-4495 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