CVE-2017-15680
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 IDOR vulnerability exists which allows unauthenticated attackers to view and modify administrative data.
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 confidenceAn IDOR (Insecure Direct Object Reference) vulnerability in Crafter CMS Crafter Studio 3.0.1 allows unauthenticated attackers to directly reference administrative objects (likely via predictable URLs or parameters) to view and modify sensitive administrative data without authentication.
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, < 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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 installedCheck for Crafter Studio web application directories, services, or running processes on the server. Common locations include /opt/crafter or similar installation directories. Look for the craftercms or crafter-studio process/service.Affected if Crafter Studio is installed and running on the system
-
Determine the installed Crafter CMS versionLocate the version file or configuration within the Crafter installation directory. Check for a version manifest, pom.xml, or build information in the Crafter Studio application files. The version is typically found in the installation root or within the WEB-INF directory of the deployed application.Affected if The installed version is 3.0.0 or any version >= 3.0 but < 3.0.1
-
Verify administrative endpoints are network-accessibleAttempt to access common Crafter Studio administrative paths without providing credentials. Typical endpoints include /studio or /crafter-studio based URLs. Use a web browser or curl to send unauthenticated requests to administrative object URLs.Affected if Administrative endpoints respond to unauthenticated requests and return administrative data or functionality
-
Check for direct object reference exposureTest predictable URL patterns for administrative objects (such as /api/1/admin/objects or similar paths) without authentication headers. Observe whether the application returns sensitive administrative data or allows modification without requiring authentication.Affected if The application returns administrative data or allows modifications without any authentication credentials
A system is affected if it runs Crafter Studio version 3.0.0 (or any version >= 3.0 but < 3.0.1) AND has unauthenticated access to administrative endpoints that expose or allow modification of sensitive data.
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
Upgrade Crafter Studio to a patched version; if upgrade is not immediately feasible, implement authentication middleware and object-level authorization checks on all administrative endpoints to prevent unauthenticated access.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-15680 — 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-15680 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