dbcve.org
Fortisoar Imap ConnectorApplication · Fortinet

CVE-2024-48890

HIGH · 8.8 CVSS v3.1 Published 2025-01-14
Fix available
A fix is available. Upgrade to 3.5.8 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
An improper neutralization of special elements used in an OS command ('OS Command Injection') vulnerability [CWE-78] in FortiSOAR IMAP connector version 3.5.7 and below may allow an authenticated attacker to execute unauthorized code or commands via a specifically crafted playbook

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 · moderate confidence

An OS Command Injection (CWE-78) vulnerability in FortiSOAR's IMAP connector versions 3.5.7 and below allows an authenticated attacker to execute arbitrary OS commands through a specially crafted playbook. The vulnerability exists in the IMAP connector's processing of playbook configurations, where insufficient input validation permits command injection.

MitigationUpgrade the FortiSOAR IMAP connector to a version above 3.5.7. Additionally, review and sanitize existing playbooks for malicious content, and limit IMAP connector permissions to the minimum required for business operations.

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
Fortisoar Imap ConnectorApplication
Affected:< 3.5.8

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 IMAP connector version
    Access FortiSOAR administration console and navigate to the connectors or extensions management section. Locate the IMAP connector and record its installed version number.
    Affected if The IMAP connector version is 3.5.7 or below
  2. Verify IMAP connector is in use
    Review the playbook list in FortiSOAR and filter for playbooks that utilize the IMAP connector. Check if any active playbooks reference IMAP actions or triggers.
    Affected if Any playbooks are actively using the IMAP connector functionality
  3. Inspect IMAP connector playbook configurations
    Examine the configuration parameters of playbooks using the IMAP connector. Review all input fields for unexpected shell metacharacters, command strings, or variable substitutions that could indicate injection payloads.
    Affected if Playbook configurations contain suspicious command injection patterns or unexpected shell syntax in IMAP-related fields

The environment is affected if the IMAP connector version is 3.5.7 or below and playbooks utilizing the IMAP connector are configured or active.

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 3.5.8 or later
Fixed in 3.5.8
Interim mitigation

Upgrade the FortiSOAR IMAP connector to a version above 3.5.7. Additionally, review and sanitize existing playbooks for malicious content, and limit IMAP connector permissions to the minimum required for business operations.

Recommended fix High confidence

3.5.8

  1. 1. Identify the currently installed FortiSOAR IMAP Connector version in your environment
  2. 2. Download FortiSOAR IMAP Connector version 3.5.8 or later from the official Fortinet repository
  3. 3. Apply the upgrade to the FortiSOAR IMAP Connector following Fortinet's standard connector update procedures
  4. 4. Verify the IMAP Connector has been successfully upgraded to version 3.5.8 or later
  5. 5. Test that IMAP connector functionality remains operational after the upgrade

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

Fix this in Fortisoar Imap Connector Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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