CVE-2022-27562
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 · uneditedUnsafe default file type filter policy in HCL Domino Volt allows upload of .html file and execution of unsafe JavaScript in deployed applications.
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 confidenceHCL Domino Volt has an unsafe default file type filter policy that permits .html file uploads. When these files are deployed within applications, the embedded JavaScript executes in users' browsers, enabling stored cross-site scripting (XSS) attacks.
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, < 1.1.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
- 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 HCL Domino Leap versionAccess the Domino Leap administration console or check the product installation directory for version information. Look for version metadata in the product header or about page.Affected if The installed version is 1.0.x or any version below 1.1.1, meaning the vulnerable default configuration applies.
-
Locate the file type filter policy configurationNavigate to the Domino Leap administration settings panel and find the file type filter or upload policy configuration section. This is typically found under Security or Application Settings.Affected if The policy shows .html files are permitted in the allowed file types list, indicating the unsafe default is in effect.
-
Verify the default filter settings are activeCheck whether the file type filter is set to use default values or a custom policy. Confirm if .html is explicitly listed as an allowed extension or if all file types are permitted.Affected if The file type filter uses default settings and permits .html file uploads without explicit restriction.
-
Review active applications for file upload capabilitiesExamine the application configuration or design elements of deployed Domino Leap applications to identify which ones have file upload controls enabled.Affected if Any application accepts file uploads and the file type filter has not been reconfigured to exclude .html files.
You are affected if Domino Leap version is below 1.1.1 AND the file type filter policy has not been modified from its default state that permits .html file uploads.
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.
dbcve · scoped1.1.1
Configure the file type filter policy in HCL Domino Volt to block .html file uploads and restrict allowed file types to safe formats (e.g., images, documents). Audit existing applications for malicious .html uploads.
HCL Domino Leap 1.1.1 or later
- 1. Back up the existing HCL Domino Leap installation and all applications/data
- 2. Download HCL Domino Leap version 1.1.1 or later from the official HCL support portal (support.hcl-software.com)
- 3. Review HCL Domino Leap 1.1.1 release notes for any prerequisites or migration considerations
- 4. Install the upgrade following HCL's standard upgrade procedure for Domino Leap
- 5. Verify the installation completed successfully
- 6. Test that .html file uploads are now blocked by the file type filter policy
- 7. Verify existing applications function correctly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- 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-27562 — 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-27562 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