CVE-2018-0687
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 · uneditedCross-site scripting vulnerability in Denbun by NEOJAPAN Inc. (Denbun POP version V3.3P R4.0 and earlier, Denbun IMAP version V3.3I R4.0 and earlier) allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.
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 confidenceCross-site scripting vulnerability in Denbun webmail allows remote attackers to inject arbitrary JavaScript or HTML through unspecified vectors. The vulnerability exists in both POP and IMAP versions up to V3.3P R4.0 and V3.3I R4.0 respectively. This is a client-side attack potentially allowing session hijacking or credential theft.
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.3i_r4.0<= 3.3p_r4.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.0/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 Denbun webmail installationIdentify whether Denbun webmail (either IMAP or POP variant) is deployed in your environment. Check for Denbun-related processes, services, or web application directories.Affected if Denbun webmail is installed and running
-
Determine the Denbun versionLocate and read the version information for your Denbun installation. This is typically displayed in the web interface login page, or found in configuration files, About pages, or system documentation provided with the installation.Affected if The version is 3.3i_r4.0 or lower (for IMAP) or 3.3p_r4.0 or lower (for POP)
-
Identify the Denbun variantDetermine whether your installation is the IMAP version (Neo Debun Imap) or the POP version (Neo Debun Pop). Check the product name or model identifier in the web interface or installation documentation.Affected if The variant is Neo Debun Imap or Neo Debun Pop and the version falls within the affected range
-
Verify web interface accessibilityConfirm that the Denbun webmail interface is accessible over HTTP/HTTPS. Since this is a client-side XSS vulnerability, the web interface must be exposed for the flaw to be exploitable.Affected if The web interface is externally or internally accessible and the version is within the affected range
You are affected if Denbun webmail (either IMAP or POP variant) is installed with a version at or below 3.3i_r4.0 (IMAP) or 3.3p_r4.0 (POP), and the web interface is accessible.
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 vendor patch or update to a version beyond V3.3P R4.0/V3.3I R4.0. Implement input validation and output encoding on all user-supplied data fields as an interim mitigation.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0687 — 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-2018-0687 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