dbcve.org
FortimanagerApplication · Fortinet

CVE-2024-52962

MEDIUM · 5.3 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 7.0.14 / 7.2.9 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 Output Neutralization for Logs vulnerability [CWE-117] in FortiAnalyzer version 7.6.1 and below, version 7.4.5 and below, version 7.2.8 and below, version 7.0.13 and below and FortiManager version 7.6.1 and below, version 7.4.5 and below, version 7.2.8 and below, version 7.0.12 and below may allow an unauthenticated remote attacker to pollute the logs via crafted login 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

This is a log injection vulnerability (CWE-117) in FortiAnalyzer and FortiManager where unauthenticated remote attackers can pollute logs by sending crafted login requests. The lack of proper output neutralization allows malicious input to be written directly into log files, potentially enabling log poisoning attacks or obscuring forensic evidence.

MitigationApply the vendor-supplied patches for FortiAnalyzer and FortiManager to upgrade to fixed versions. Upgrade to FortiAnalyzer 7.6.2+, 7.4.6+, 7.2.9+, 7.0.14+ and FortiManager 7.6.2+, 7.4.6+, 7.2.9+, 7.0.13+ as appropriate.

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
FortimanagerApplication
Affected:>= 7.0.0, < 7.0.14>= 7.2.0, < 7.2.9>= 7.4.0, < 7.4.6>= 7.6.0, < 7.6.2
FortianalyzerApplication
Affected:>= 7.0.0, < 7.0.14>= 7.2.0, < 7.2.9>= 7.4.0, < 7.4.6>= 7.6.0, < 7.6.2

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Identify the installed product
    Run 'get system status' in the FortiAnalyzer/FortiManager CLI or check the web UI dashboard to confirm whether you are running FortiAnalyzer or FortiManager
    Affected if The product is FortiAnalyzer or FortiManager
  2. Check the installed version
    Run 'get system status' in the CLI and locate the 'FortiAnalyzer/FortiManager version' field, or view the version displayed on the web UI login page or dashboard
    Affected if The version displayed matches any of the following ranges: 7.0.0 through 7.0.13, 7.2.0 through 7.2.8, 7.4.0 through 7.4.5, or 7.6.0 through 7.6.1
  3. Confirm the build number
    Run 'get system status' and note the 'Build' number shown in the output
    Affected if The build number corresponds to an affected version within the ranges listed above

You are affected if your FortiAnalyzer or FortiManager version falls within 7.0.0-7.0.13, 7.2.0-7.2.8, 7.4.0-7.4.5, or 7.6.0-7.6.1, regardless of build number within those ranges.

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 7.0.14 / 7.2.9 / 7.4.6 or later
Fixed in 7.0.147.2.97.4.6
Interim mitigation

Apply the vendor-supplied patches for FortiAnalyzer and FortiManager to upgrade to fixed versions. Upgrade to FortiAnalyzer 7.6.2+, 7.4.6+, 7.2.9+, 7.0.14+ and FortiManager 7.6.2+, 7.4.6+, 7.2.9+, 7.0.13+ as appropriate.

Recommended fix High confidence

FortiManager/FortiAnalyzer: Upgrade to 7.0.14, 7.2.9, 7.4.6, or 7.6.2 (or later stable releases within your major version branch)

  1. 1. Identify the current FortiManager/FortiAnalyzer firmware version by navigating to System Settings > Firmware or using 'get system status' CLI command.
  2. 2. Review the Fortinet release notes for the target fixed version (7.0.14, 7.2.9, 7.4.6, or 7.6.2) to confirm compatibility with your deployment model.
  3. 3. Create a full backup of the FortiManager/FortiAnalyzer configuration using the GUI (System Settings > Backup) or CLI 'execute backup full-config' command.
  4. 4. Download the appropriate firmware image from Fortinet Support portal (https://support.fortinet.com/).
  5. 5. Upload the firmware image via GUI (System Settings > Firmware > Upload) or CLI 'execute system firmware upgrade' command.
  6. 6. Reboot the device and verify all services are operational after upgrade.
  7. 7. Validate that log entries are properly sanitized and no log injection occurs with the fixed version.
Caveat Review Fortinet release notes for potential configuration changes and ensure compatibility with integrated FortiGate devices before upgrading.

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

Fix this in Fortimanager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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