CVE-2018-12353
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 · uneditedKnowage (formerly SpagoBI) 6.1.1 allows XSS via the name field to the "Business Model's Catalogue" catalogue.
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 confidenceKnowage 6.1.1 contains a stored Cross-Site Scripting (XSS) vulnerability in the name field of the Business Model's Catalogue feature. An attacker with access to this field can inject malicious JavaScript that executes when other users view the catalogue.
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= 6.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
- 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.
-
Identify installed Knowage versionCheck the Knowage application version through the admin panel, about page, or version file in the installation directory. Common locations include the WAR file metadata, system info page, or configuration files.Affected if The installed version is exactly Knowage 6.1.1 (exact match required per affected version range)
-
Confirm Business Model Catalogue feature is enabledAccess the Knowage admin console or feature configuration. Navigate to the Business Model Catalogue section under the KNOWAGE Suite or Business Modeling menu to verify the feature is accessible.Affected if The Business Model Catalogue feature is present and enabled in the installation
-
Check user permissions for Business Model accessReview user roles and permissions in the Knowage administration panel. Determine if standard users or untrusted users have create or edit access to the Business Model Catalogue.Affected if Users with limited trust or external-facing accounts have write access to the Business Model Catalogue name field
-
Inspect Business Model name fields for malicious contentQuery the Knowage database or use the admin interface to list all Business Models in the catalogue. Examine the name field values for suspicious patterns such as script tags, event handlers (onerror, onload), or encoded JavaScript.Affected if Any Business Model entry contains unsanitized script tags or JavaScript in the name field
You are affected if running exactly Knowage 6.1.1 with the Business Model Catalogue feature enabled and users have the ability to create or edit Business Model names.
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 name field in the Business Model's Catalogue. Apply context-aware escaping before rendering user-supplied content and consider Content Security Policy headers as a defense-in-depth measure.
- Consultation4.0 h
- Implementation6.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-12353 — 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-12353 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