CVE-2018-1000547
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 · uneditedcoreBOS version 7.0 and earlier contains a Incorrect Access Control vulnerability in Module: Contacts that can result in The error allows you to access records that you have no permissions to. .
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 confidencecoreBOS version 7.0 and earlier contains an Incorrect Access Control vulnerability in the Contacts module that allows authenticated users to access contact records they do not have permission to view. This appears to be a broken access control or insecure direct object reference (IDOR) issue where proper authorization checks are missing when accessing specific contact records.
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<= 7.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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 coreBOS versionAccess the coreBOS admin panel or check the version.php file in the installation directory to determine the exact version number.Affected if Version is 7.0 or any version lower than 7.0 (e.g., 6.x, 5.x)
-
Confirm Contacts module is activeLog into coreBOS as an administrator and navigate to the module list to verify the Contacts module is installed and enabled.Affected if The Contacts module exists and is enabled in the system
-
Verify user role and permission configurationAccess the coreBOS admin panel, navigate to Users > Roles and verify the role assignments for the test user account you will use to check access controls.Affected if A user with limited role permissions exists in the system
-
Test unauthorized contact record accessCreate or use a test user with restricted permissions (e.g., a user assigned to a different organization or without visibility to certain contacts). Log in as that user and attempt to access a contact record that belongs to another user or organization using a direct record ID URL.Affected if The user can view contact records they were not explicitly granted permission to access, indicating missing authorization checks
You are affected if your coreBOS version is 7.0 or lower and authenticated users can access contact records without proper permission validation in the Contacts module.
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 authorization checks in the Contacts module to verify user permissions before allowing access to records. Ensure all record access operations validate that the current user has appropriate permissions for the requested resource.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000547 — 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-1000547 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