CVE-2022-31200
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 · uneditedAtmail 5.62 allows XSS via the mail/parse.php?file=html/$this-%3ELanguage/help/filexp.html&FirstLoad=1&HelpFile=file.html Search Terms field.
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 confidenceAtmail 5.62 contains a Cross-Site Scripting (XSS) vulnerability in the mail/parse.php endpoint. The Search Terms field does not properly sanitize user input before rendering it in the HelpFile parameter context, allowing an attacker to inject malicious JavaScript code that executes in the victim's browser.
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= 5.62CVSS 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 Atmail installationLocate Atmail web application files. Check common installation paths such as /var/www/html/atmail, /home/atmail/public_html, or the web server's document root. Look for the presence of atmail directories and the mail/parse.php file.Affected if Atmail is installed on the system and the mail/parse.php file exists in the web directory structure.
-
Identify Atmail versionExamine the version file or about page within the Atmail installation. Common locations include a version.php file, composer.json, or the administrative interface's system information section. Alternatively, check the HTTP response headers from the Atmail login page for version indicators.Affected if The installed Atmail version is exactly 5.62.
-
Verify mail/parse.php endpoint existsAccess the file system and confirm mail/parse.php exists within the Atmail web root. If the file exists, it indicates the vulnerable component is present.Affected if The file mail/parse.php exists in the Atmail installation directory.
-
Check for HelpFile parameter handlingReview the source code of mail/parse.php to identify how the HelpFile parameter is processed and whether it accepts user-supplied input that could be rendered in an HTML context.Affected if The HelpFile parameter is used in the application and accepts user input that is reflected back in the response.
-
Confirm Search Terms field is functionalAccess the Atmail web interface and navigate to the functionality that utilizes the Search Terms field. This is typically found in the mail search or help documentation features that interact with the parse.php endpoint.Affected if The Search Terms field is accessible and accepts user input that gets passed to the HelpFile parameter context.
You are affected if Atmail version 5.62 is installed and the mail/parse.php endpoint with its Search Terms and HelpFile parameter functionality is accessible and in use.
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 the Search Terms field and HelpFile parameter. Apply context-aware escaping when rendering user-supplied data in HTML. Consider deploying a WAF rule to detect and block XSS attempts while remediation is underway.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-31200 — 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-31200 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