CVE-2018-15635
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 the Discuss App of Odoo Community 12.0 and earlier, and Odoo Enterprise 12.0 and earlier allows remote attackers to inject arbitrary web script in the browser of an internal user of the system by tricking them into inviting a follower on a document with a crafted name.
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 confidenceCross-site scripting vulnerability in Odoo 12.0 and earlier in the Discuss App allows remote attackers to inject arbitrary JavaScript by tricking internal users into inviting a follower on a document with a crafted name. The document name is rendered without proper sanitization in the follower invitation context.
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<= 12.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.
-
Check installed Odoo versionAccess Odoo and navigate to Apps menu, or check the Odoo server log on startup which displays the version number, or query the 'ir_module_module' table in the database for the 'base' module versionAffected if The installed version is 12.0 or any version earlier than 12.0
-
Verify Discuss App is installedLog into Odoo as administrator and navigate to the Apps dashboard, then search for 'Discuss' or check the 'ir_module_module' database table for module name 'mail' which provides Discuss functionalityAffected if The Discuss/mail module is installed and accessible to users
-
Confirm follower invitation feature existsAccess the Discuss App, create or open any document (like a Project, Task, or Document), and locate the 'Share' or 'Invite Follower' button in the document's form viewAffected if The follower invitation feature is present and usable in documents
-
Inspect document name rendering in invitation flowIn a document with the Discuss App enabled, click the Invite Follower option and examine how the document name appears in the invitation interface - check if the name field is rendered with proper HTML encoding in the invitation dialog or notificationAffected if Document names are displayed in the invitation interface without visible HTML entity encoding (e.g., <script> tags would render as literal text if properly escaped, but would execute if not)
Environment is affected if running Odoo version 12.0 or earlier AND the Discuss App with follower invitation functionality is installed and operational, as the XSS vulnerability exists in how document names are rendered during follower invitation.
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 output encoding/escaping when rendering document names in the Discuss App's follower invitation feature to prevent XSS execution.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-15635 — 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-15635 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