dbcve.org
FortivoiceApplication · Fortinet

CVE-2023-37931

HIGH · 8.8 CVSS v3.1 Published 2025-01-14
Fix available
A fix is available. Upgrade to 6.4.9 / 7.0.2 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 sql command ('sql injection') vulnerability [CWE-88] in FortiVoice Entreprise version 7.0.0 through 7.0.1 and before 6.4.8 allows an authenticated attacker to perform a blind sql injection attack via sending crafted HTTP or HTTPS 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

A blind SQL injection vulnerability in FortiVoice Enterprise web interface allows authenticated attackers to inject arbitrary SQL commands via crafted HTTP/HTTPS requests. The flaw exists in versions 7.0.0 through 7.0.1 and versions before 6.4.8.

MitigationApply Fortinet's vendor patches by upgrading to FortiVoice Enterprise 7.0.2 or later, or 6.4.8 or later, as specified in the official security advisory.

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
FortivoiceApplication
Affected:>= 6.0.0, < 6.4.9>= 7.0.0, < 7.0.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
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 FortiVoice Enterprise version
    Log into the FortiVoice web interface as administrator and navigate to System > FortiGuard or check the dashboard for the firmware version. Alternatively, access the CLI and run the command 'get system status' to retrieve the exact version number.
    Affected if The installed version falls within 6.0.0 to 6.4.8 inclusive, or 7.0.0 to 7.0.1 inclusive.
  2. Confirm web interface is enabled
    In the FortiVoice web interface, go to System > Network > Interface or check the administrative access settings to verify that HTTPS or HTTP access is enabled for the management interface.
    Affected if The web interface (HTTPS/HTTP administrative access) is enabled and accessible.
  3. Verify authentication to web interface
    Attempt to access the FortiVoice login page using the management IP address. Confirm that valid administrator credentials exist and can log in.
    Affected if An administrator account exists and can authenticate to the web interface, meaning the SQL injection payload could be delivered by an authenticated attacker.

You are affected if your FortiVoice Enterprise version is 6.0.0 through 6.4.8 or 7.0.0 through 7.0.1, the web interface is enabled, and you have administrator accounts configured.

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 6.4.9 / 7.0.2 or later
Fixed in 6.4.97.0.2
Interim mitigation

Apply Fortinet's vendor patches by upgrading to FortiVoice Enterprise 7.0.2 or later, or 6.4.8 or later, as specified in the official security advisory.

Recommended fix High confidence

FortiVoice 6.4.9 (for 6.x branch) or 7.0.2 (for 7.x branch) - latest stable release in respective branch recommended

  1. 1. Obtain the latest FortiVoice firmware from Fortinet's support portal (fortinet.com/support)
  2. 2. Review the release notes for version 6.4.9 (for 6.x branch) or 7.0.2 (for 7.x branch) to confirm the security fix and check for any known issues
  3. 3. Backup the current FortiVoice configuration via the web UI (System > Maintenance > Backup & Restore) or CLI
  4. 4. Upload and install the new firmware version through the web UI (System > Maintenance > Firmware) or CLI using the 'execute system firmware upgrade' command
  5. 5. After upgrade, verify the system is operational and confirm the new version is running with 'get system status' CLI command
  6. 6. Restore the configuration if needed and validate all services are functioning properly
Caveat Review release notes for any configuration or feature changes between versions; test in staging environment before production deployment

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

Fix this in Fortivoice Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,950
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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