dbcve.org
Command CentreApplication · Gallagher

CVE-2024-21838

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-05
Fix available
A fix is available. Upgrade to 8.70.2526 / 8.80.1526 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Improper neutralization of special elements in output (CWE-74) used by the email generation feature of the Command Centre Server could lead to HTML code injection in emails generated by Command Centre. This issue affects: Gallagher Command Centre 9.00 prior to vEL9.00.1774 (MR2), 8.90 prior to vEL8.90.1751 (MR3), 8.80 prior to vEL8.80.1526 (MR4), 8.70 prior to vEL8.70.2526 (MR6),  all version of 8.60 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 confidence

The email generation feature in Gallagher Command Centre Server improperly neutralizes special elements, allowing HTML code injection (CWE-74). Attackers could craft malicious input that gets rendered in generated emails, potentially leading to phishing or credential theft via email-based attacks.

MitigationApply the vendor-supplied patches: upgrade to vEL9.00.1774 (MR2), vEL8.90.1751 (MR3), vEL8.80.1526 (MR4), or vEL8.70.2526 (MR6) or later. For versions 8.60 and prior, upgrade to a supported version.

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 CentreApplication
Affected:<= 8.60>= 8.70, < 8.70.2526>= 8.80, < 8.80.1526>= 8.90, < 8.90.1751>= 9.00, < 9.00.1774

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
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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

  1. Check Gallagher Command Centre server version
    Log into the Command Centre client or admin interface, then navigate to Help > About, or check the server's installation directory for a version file. The version is also visible in the Gallagher Command Centre login screen banner.
    Affected if The installed version falls within any of these ranges: <= 8.60, >= 8.70 and < 8.70.2526, >= 8.80 and < 8.80.1526, >= 8.90 and < 8.90.1751, or >= 9.00 and < 9.00.1774.
  2. Verify email generation feature is configured
    Open the Command Centre admin interface and navigate to System > Options > Email, or look for email-related configuration sections where email templates, notifications, or SMTP settings are defined.
    Affected if Email generation is enabled and configured, as the vulnerability exists in how the system processes input within email templates.
  3. Inspect email template configuration files
    If accessible, examine the email template configuration files or database records that store email body content. Look for any custom templates or dynamic fields that accept user input.
    Affected if Custom email templates or dynamic content injection points exist that could contain unsanitized HTML input.

You are affected if your Command Centre version is within the vulnerable ranges AND the email generation feature is enabled with custom templates or dynamic content.

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 8.70.2526 / 8.80.1526 / 8.90.1751 or later
Fixed in 8.70.25268.80.15268.90.1751
Interim mitigation

Apply the vendor-supplied patches: upgrade to vEL9.00.1774 (MR2), vEL8.90.1751 (MR3), vEL8.80.1526 (MR4), or vEL8.70.2526 (MR6) or later. For versions 8.60 and prior, upgrade to a supported version.

Recommended fix High confidence

Upgrade to one of: vEL9.00.1774 (MR2) or later for v9.x; vEL8.90.1751 (MR3) or later for v8.90; vEL8.80.1526 (MR4) or later for v8.80; vEL8.70.2526 (MR6) or later for v8.70; Note: v8.60 and prior have no fix path - must upgrade to a supported version

  1. 1. Identify the current installed version of Gallagher Command Centre (Help > About in the client, or check the server's version information)
  2. 2. Determine which upgrade path applies based on your current version (8.60 and prior; 8.70.x; 8.80.x; or 8.90.x)
  3. 3. Plan maintenance window for the upgrade - this affects the Command Centre Server
  4. 4. Perform a full backup of the Command Centre database and configuration per standard backup procedures
  5. 5. Download the appropriate fixed release from Gallagher (see upgrade_path)
  6. 6. Apply the upgrade following Gallagher's standard upgrade documentation for your version
  7. 7. After upgrade, verify the email generation feature works correctly and that the fix is applied by testing email output

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

Fix this in Command Centre Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-21838 — 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-2024-21838 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