dbcve.org
FortisiemApplication · Fortinet

CVE-2024-52969

MEDIUM · 6.5 CVSS v3.1 Published 2025-01-14
Fix available
A fix is available. Upgrade to after 7.1.7 or later.
See remediation →
71/100
Remediation priority · Elevated
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 SQL Command ('SQL Injection') vulnerability [CWE-89] in FortiSIEM ersion 7.1.7 and below, version 7.1.0, version 7.0.3 and below, version 6.7.9 and below, 6.7.8, version 6.6.5 and below, version 6.5.3 and below, version 6.4.4 and below Update/Create Case feature may allow an authenticated attacker to extract database information via crafted requests.

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

SQL injection vulnerability in FortiSIEM's Update/Create Case feature allows authenticated attackers to inject malicious SQL commands via crafted requests, enabling extraction of sensitive database information. The vulnerability stems from improper neutralization of special elements in SQL queries.

MitigationApply vendor patches released for FortiSIEM to address this vulnerability. Until patches are applied, limit access to the Case management feature to trusted users only and monitor for suspicious database queries.

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
FortisiemApplication
Affected:>= 6.4.0, <= 7.1.7

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
None
Availability
None

CVSS:3.1/AV:N/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 checks

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

  1. Identify FortiSIEM installation version
    Locate the FortiSIEM version information via the web UI (System > Settings > About) or by running the command 'phoenixmanger.sh get system status' or 'fnsysctl get system status' from the supervisor CLI, depending on deployment architecture
    Affected if The installed version falls within the range 6.4.0 through 7.1.7 inclusive
  2. Confirm Case management feature is enabled
    Check FortiSIEM configuration to determine if the Case management module is active. This may be visible in the UI under Analytics > Case or via configuration files that control feature enablement
    Affected if The Case management feature is enabled and accessible to users
  3. Verify authentication access to Case functionality
    Review user accounts and roles that have permissions to access the Update/Create Case feature. Check if untrusted or low-privilege accounts can reach this endpoint
    Affected if Users with limited or untrusted privileges can access the Update/Create Case functionality
  4. Audit logs for anomalous SQL queries
    Search FortiSIEM event logs and database audit trails for unusual or malformed SQL statements, especially those containing UNION statements, subqueries, or database system table references (e.g., information_schema) originating from Case management operations
    Affected if Unexpected SQL query patterns appear in logs originating from Case management operations

A FortiSIEM instance is affected if it runs version 6.4.0 through 7.1.7 and the Case management feature is accessible to authenticated users who could inject malicious SQL commands.

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 a release after 7.1.7
Interim mitigation

Apply vendor patches released for FortiSIEM to address this vulnerability. Until patches are applied, limit access to the Case management feature to trusted users only and monitor for suspicious database queries.

Recommended fix High confidence

FortiSIEM 7.1.8 or later (recommended: latest available stable release)

  1. 1. Identify the current FortiSIEM version by navigating to Admin > System Settings > System Control in the FortiSIEM web UI
  2. 2. Confirm the version falls within the affected range (6.4.0 - 7.1.7)
  3. 3. Plan for an upgrade to a fixed release. According to FortiGuard advisories, FortiSIEM 7.1.8 and later releases contain the fix for this SQL injection vulnerability (CVE-2024-52969)
  4. 4. Review FortiSIEM upgrade documentation and release notes for the target version before proceeding
  5. 5. Perform a full backup of the FortiSIEM environment, including configuration and event data
  6. 6. Execute the upgrade following Fortinet's recommended upgrade path from the current version to the fixed release
  7. 7. After upgrade, verify the FortiSIEM version reflects the fixed release
  8. 8. Test the Update/Create Case functionality to confirm the SQL injection vulnerability is resolved
Caveat Minor: Review release notes for any configuration or behavior changes between current and fixed versions; test in staging before production deployment

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

Fix this in Fortisiem Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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