CVE-2023-22902
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 · uneditedOpenfind Mail2000 file uploading function has insufficient filtering for user input. An authenticated remote attacker with general user privilege can exploit this vulnerability to inject JavaScript, conducting an XSS attack.
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 confidenceOpenfind Mail2000's file upload function lacks proper input filtering, allowing authenticated users with general privileges to inject malicious JavaScript through uploaded files. This XSS vulnerability occurs because the system doesn't sanitize file names or potentially file content before rendering them in the web interface.
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= 7.0= 8.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
- 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.
-
Identify the installed Mail2000 versionCheck the product version through the web admin interface, system information page, or version lookup command provided by Openfind. Look for exact version strings 7.0 or 8.0.Affected if The installed version is exactly 7.0 or exactly 8.0 (not patched later versions).
-
Confirm file upload functionality is accessibleLog in as a user with general privileges (non-admin) and navigate to the file upload feature. Verify the upload interface is available and accepts file submissions.Affected if General authenticated users can access and use the file upload function.
-
Verify uploaded files are displayed in the web interfaceUpload a test file through the interface, then navigate to the file listing or attachment view. Check if file names are rendered and displayed in the web UI without sanitization.Affected if Uploaded file names are rendered and visible to users in the web interface (this is where XSS would trigger).
-
Check if file content is rendered inlineAfter uploading a file, attempt to view or preview it through the browser. Determine if the system renders file content directly or forces download via content-disposition: attachment header.Affected if File content is rendered inline in the browser rather than being forced as a download (increases XSS impact).
If the environment runs Openfind Mail2000 version 7.0 or 8.0, allows authenticated general users to upload files, and displays uploaded file names in the web interface without sanitization, the environment is affected by this XSS vulnerability.
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 comprehensive input validation and output encoding for all file upload parameters. Sanitize file names and any user-supplied content that gets displayed, using context-appropriate XSS filtering. Consider implementing a content-disposition: attachment header for uploaded files to prevent inline rendering.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22902 — 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-22902 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