CVE-2023-25074
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 · uneditedImproper privilege validation in Command Centre Server allows authenticated unprivileged operators to modify and view Competencies. This issue affects Command Centre: vEL8.90 prior to vEL8.90.1318 (MR1), vEL8.80 prior to vEL8.80.1192 (MR2), vEL8.70 prior to vEL8.70.2185 (MR4), vEL8.60 prior to vEL8.60.2347 (MR6), vEL8.50 prior to vEL8.50.2831 (MR8), all versions vEL8.40 and prior.
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 confidenceThis is an authorization bypass vulnerability in Gallagher Command Centre Server where the application fails to properly validate user privileges before allowing access to Competencies functionality. An authenticated user with only basic/limited operator privileges can view and modify Competencies that should be restricted to higher-privileged administrators.
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<= 8.40.2216>= 8.50, < 8.50.2831>= 8.60, < 8.60.2347>= 8.70, < 8.70.2185>= 8.80, < 8.80.1192>= 8.90, < 8.90.1318CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 installed Command Centre versionAccess the Gallagher Command Centre admin interface and navigate to Help > About, or check the Windows Programs and Features list for the installed version numberAffected if The installed version falls within any of these ranges: <= 8.40.2216, >= 8.50 and < 8.50.2831, >= 8.60 and < 8.60.2347, >= 8.70 and < 8.70.2185, >= 8.80 and < 8.80.1192, >= 8.90 and < 8.90.1318
-
Confirm user role assignment for testLog in as a basic or limited operator account (non-administrator) and verify the assigned privilege level in User Admin > OperatorsAffected if The test account has only basic or limited operator privileges, not administrator-level access
-
Verify Competencies access for low-privilege userUsing the basic/limited operator account, attempt to access the Competencies module via the navigation menu or direct URL within the Command Centre web interfaceAffected if The low-privilege user can view, modify, or delete Competencies that should be restricted to administrators
-
Review Competencies permissions configurationAs an administrator, inspect the Competencies module permissions in Config > System Options > Competencies to confirm which security groups have accessAffected if The Competencies permissions allow access by basic or limited operator security groups
A user is affected if the Command Centre version is within the affected ranges and a basic/limited operator account can access Competencies functionality that should require administrator privileges.
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.
dbcve · scoped8.50.28318.60.23478.70.2185
Apply the vendor-supplied patches for the specific version (vEL8.90.1318+, vEL8.80.1192+, vEL8.70.2185+, vEL8.60.2347+, or vEL8.50.2831+) to address the improper privilege validation. Verify that unprivileged operator accounts can no longer access Competencies functions after patching.
Upgrade to the minimum fixed version for your branch: vEL8.50.2831+, vEL8.60.2347+, vEL8.70.2185+, vEL8.80.1192+, or vEL8.90.1318+
- Identify the current installed version of Gallagher Command Centre by checking the server or administrative interface.
- Determine which version branch is currently in use (vEL8.40 and prior, vEL8.50, vEL8.60, vEL8.70, vEL8.80, or vEL8.90).
- For vEL8.40 and prior versions: upgrade to vEL8.50.2831 (MR8) or later recommended.
- For vEL8.50.x versions: upgrade to vEL8.50.2831 (MR8) or later.
- For vEL8.60.x versions: upgrade to vEL8.60.2347 (MR6) or later.
- For vEL8.70.x versions: upgrade to vEL8.70.2185 (MR4) or later.
- For vEL8.80.x versions: upgrade to vEL8.80.1192 (MR2) or later.
- For vEL8.90.x versions: upgrade to vEL8.90.1318 (MR1) or later.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-25074 — 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-2023-25074 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