dbcve.org
Command Centre MobileApplication · Gallagher

CVE-2025-47147

MEDIUM · 5.7 CVSS v3.1 Published 2026-03-03
Fix available
A fix is available. Upgrade to 9.40.123 or later.
See remediation →
59/100
Remediation priority · Elevated
Zero-click

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 · unedited
Cleartext Storage of Sensitive Information (CWE-312) in the Command Centre Mobile Client on Android and iOS could allow an attacker with access to a logged-in Operator's mobile device to extract the session token and exploit access for a limited duration. This issue affects Command Centre Mobile Client versions prior to 9.40.123.

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 confidence

The Command Centre Mobile Client for Android and iOS stores session tokens in cleartext (unencrypted) format on the device. An attacker with physical or logical access to a logged-in Operator's mobile device can read these cleartext session tokens from local storage and exploit them for limited-duration access to the Command Centre system.

MitigationUpgrade Command Centre Mobile Client to version 9.40.123 or later, which implements secure storage mechanisms (encrypted storage using platform keychains/keystores) for session tokens.

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
Command Centre MobileApplication
Affected:< 9.40.123

CVSS 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
High
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed version of Command Centre Mobile Client
    On Android: Open Google Play Store app page, scroll to 'App version' under 'Version'; On iOS: Open App Store app page, tap version number under 'Version' - or go to device Settings > Apps > Command Centre Mobile > Version
    Affected if Version is below 9.40.123 (the fix version)
  2. Confirm app is actually Command Centre Mobile Client
    Verify the installed application name matches 'Command Centre Mobile' from Gallagher (the vendor) - check app icon, name, and publisher in the app store listing or device app settings
    Affected if The app is Command Centre Mobile Client and version is below 9.40.123
  3. Check if mobile device management (MDM) or EDR tools can inspect app storage
    If your organization uses MDM (Intune, Jamf, etc.) or mobile security tools, check if they have visibility into app-local storage configurations or can report on data protection status of installed apps
    Affected if MDM reporting shows the app lacks encryption or secure storage flags for Command Centre Mobile Client
  4. Review vendor release notes for version confirmation
    Access Gallagher Command Centre release notes or security advisories to confirm the exact version 9.40.123 as the fix for this cleartext session token issue
    Affected if Your installed version predates the 9.40.123 release containing the security fix

You are affected if Command Centre Mobile Client is installed on any Android or iOS device at a version lower than 9.40.123, where session tokens are stored unencrypted in local storage.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 9.40.123 or later
Fixed in 9.40.123
Interim mitigation

Upgrade Command Centre Mobile Client to version 9.40.123 or later, which implements secure storage mechanisms (encrypted storage using platform keychains/keystores) for session tokens.

Recommended fix High confidence

9.40.123

  1. Check the current version of Command Centre Mobile Client installed on the Android or iOS device
  2. For Android: Open Google Play Store, search for Command Centre Mobile, and tap Update if version is below 9.40.123
  3. For iOS: Open Apple App Store, search for Command Centre Mobile, and tap Update if version is below 9.40.123
  4. Alternatively, uninstall and reinstall the app from the respective app store to ensure the latest version is installed
  5. After updating, verify the app version shows 9.40.123 or later in the app's about or settings section

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Command Centre Mobile Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-47147 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-47147 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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