CVE-2015-5640
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 · uneditedbaserCMS before 3.0.8 allows remote authenticated users to modify arbitrary user settings via a crafted request.
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 confidencebaserCMS before version 3.0.8 contains an authorization flaw where authenticated users can modify arbitrary user settings through crafted requests. This appears to be an Insecure Direct Object Reference (IDOR) or insufficient authorization check allowing any authenticated user to access and modify other users' profile settings.
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.7CVSS 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
- Authentication
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/C:P/I:P/A:P
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 baserCMS versionLocate the version file or config file. Common locations include: /app/Config/core.php (look for 'App.version' or 'baserVersion'), /lib/Baser/Config/version.php, or check the VERSION file in the root directory. Run: `grep -r "version" /path/to/basercms/app/Config/` or inspect the admin dashboard footer which often displays the version.Affected if The installed version is 3.0.7 or lower (any version <= 3.0.7).
-
Confirm user authentication is enabledCheck if the user management module is active. Log into the baserCMS admin panel and navigate to the Users management section, or inspect the database table 'users' to confirm at least one user account exists beyond the default administrator.Affected if User authentication is enabled and user accounts exist (which is the default configuration).
-
Verify the profile editing functionality existsAccess the user management area in the baserCMS admin panel (typically /admin/users/index or /baser/admin/users/). Check for the ability to edit user profiles. Inspect the URL patterns when editing users - look for direct object references like /users/edit/[user_id].Affected if The user edit functionality is accessible and uses direct object references (ID-style URLs) without additional authorization checks.
-
Test for IDOR in profile modificationCreate two test users (or use an existing non-admin user). Log in as User A, then attempt to modify User B's profile by crafting a request to the edit endpoint with User B's ID parameter. Check if the application accepts the modification without verifying that User A owns that profile.Affected if An authenticated user can successfully modify another user's profile settings by manipulating the user ID parameter in the request.
A user is affected if baserCMS version is 3.0.7 or lower AND user authentication is enabled, as the IDOR vulnerability allows any authenticated user to modify arbitrary user profiles.
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 dataUpgrade baserCMS to version 3.0.8 or later which contains the fix for this authorization bypass vulnerability.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5640 — 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-2015-5640 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