CVE-2017-15682
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 · uneditedIn Crafter CMS Crafter Studio 3.0.1 an unauthenticated attacker is able to inject malicious JavaScript code resulting in a stored/blind XSS in the admin panel.
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 confidenceIn Crafter CMS Crafter Studio 3.0.1, an unauthenticated attacker can inject malicious JavaScript code that gets stored in the system and executes when administrators access the affected area, resulting in a stored/blind XSS vulnerability in the admin panel.
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.0.0, < 3.0.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.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.
-
Identify if Crafter CMS is installedLook for Crafter CMS installation directories (common paths: /opt/crafter, /crafter, or C:/crafter), or check running processes for 'crafter' or 'tomcat' serving Crafter applications. Inspect the file system for crafter-specific directories like 'bin', 'data', 'logs', 'crafter-studio'.Affected if Crafter CMS is present on the system
-
Determine the installed Crafter CMS versionCheck for version files in the installation directory. Common locations: {install_dir}/crafter-authoring/bin/crafter.sh version, {install_dir}/VERSION, or the Crafter Studio admin panel footer which often displays the version. Alternatively, check pom.xml or gradle files if source code is available.Affected if The installed version is 3.0.0 (any build) or any version strictly less than 3.0.1 within the 3.0.x line
-
Confirm Crafter Studio admin panel accessibilityAttempt to access the Crafter Studio login page (typically at /studio or /crafter-studio on the server port, commonly 8080). The vulnerability is exploitable by unauthenticated attackers, so no login is needed to inject the payload.Affected if Crafter Studio admin interface is reachable and exposes input fields that accept user-supplied content (such as form submissions, comments, or site content creation areas)
-
Inspect for existing malicious scripts in stored contentReview the Crafter CMS database or content repository for any unexpected or suspicious script tags, JavaScript URIs, or event handler attributes in user-contributed fields. Check tables related to content objects, comments, or user profiles in the database (usually found in {install_dir}/data/db/crafter.sqlite or MySQL/PostgreSQL if configured).Affected if Stored content contains unsanitized HTML/JavaScript that could execute when viewed by administrators
A user is affected if Crafter CMS version 3.0.0 is installed (any build) and the Crafter Studio admin panel is accessible, as this combination allows the stored XSS to be injected and later triggered when administrators access the compromised content.
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 data3.0.1
Implement proper input validation and output encoding for all user-supplied content rendered in the admin panel, and upgrade to a patched version if available.
- 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-2017-15682 — 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-2017-15682 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