CVE-2022-26348
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 · uneditedCommand Centre Server is vulnerable to SQL Injection via Windows Registry settings for date fields on the server. The Windows Registry setting allows an attacker using the Visitor Management Kiosk, an application designed for public use, to invoke an arbitrary SQL query that has been preloaded into the registry of the Windows Server to obtain sensitive information. This issue affects: Gallagher Command Centre 8.60 versions prior to 8.60.1652; 8.50 versions prior to 8.50.2245; 8.40 versions prior to 8.40.2216; 8.30 versions prior to 8.30.1470; version 8.20 and prior versions.
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 confidenceGallagher Command Centre Server contains a SQL injection vulnerability in the Windows Registry settings handling for date fields, exploitable through the Visitor Management Kiosk public-facing application. An attacker can invoke arbitrary preloaded SQL queries stored in the Windows Registry to extract sensitive information from the database.
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.20>= 8.30, < 8.30.1470>= 8.40, < 8.40.2216>= 8.50, < 8.50.2245>= 8.60, < 8.60.1652CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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.
-
Check installed Gallagher Command Centre versionLocate the Command Centre installation directory and find the version information, typically in an 'about' or 'version' file, or check the Windows Programs and Features list for the installed version.Affected if The installed version is <= 8.20, or >= 8.30 but < 8.30.1470, or >= 8.40 but < 8.40.2216, or >= 8.50 but < 8.50.2245, or >= 8.60 but < 8.60.1652.
-
Confirm Visitor Management Kiosk is enabledCheck the Command Centre configuration or admin interface to determine if the Visitor Management Kiosk module or application is currently enabled or deployed.Affected if Visitor Management Kiosk is enabled and accessible, particularly if it is publicly exposed.
-
Inspect Windows Registry permissionsUse Windows Registry Editor (regedit) or icacls to examine the access control permissions on registry keys related to Gallagher Command Centre, particularly those handling date field settings.Affected if Non-admin or unauthorized users have Write or Full Control permissions to Command Centre registry keys, allowing them to inject SQL queries.
-
Review registry keys for suspicious SQL contentExamine Windows Registry keys under the Gallagher Command Centre hive for unexpected or malformed values that may contain SQL query strings, particularly in settings related to date fields or kiosk configurations.Affected if Unexpected SQL statements or query fragments are found stored in registry values where only date values should exist.
You are affected if your Command Centre version falls within the vulnerable ranges AND the Visitor Management Kiosk is enabled with insufficiently restricted Windows Registry permissions allowing injection of SQL queries.
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.30.14708.40.22168.50.2245
Update Gallagher Command Centre to version 8.60.1652, 8.50.2245, 8.40.2216, or 8.30.1470 or later to patch the vulnerability, and restrict Windows Registry access permissions to prevent unauthorized query injection.
Upgrade to 8.30.1470 (or later 8.30.x), 8.40.2216 (or later 8.40.x), 8.50.2245 (or later 8.50.x), or 8.60.1652 (or later 8.60.x) - preferably the latest stable release in your version branch
- Identify the currently installed Gallagher Command Centre version by checking in the application or system information
- Determine which version branch (8.30, 8.40, 8.50, or 8.60) you are currently running
- Upgrade to the minimum fixed version for your branch: 8.30.1470 (if on 8.30.x), 8.40.2216 (if on 8.40.x), 8.50.2245 (if on 8.50.x), or 8.60.1652 (if on 8.60.x)
- Alternatively, upgrade to the latest available version which will contain the security fix
- Review release notes for upgrade prerequisites and ensure system requirements are met
- Perform the upgrade following Gallagher's standard upgrade procedures
- Verify the installation was successful and the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26348 — 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-2022-26348 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