dbcve.org
FortiwebApplication · Fortinet

CVE-2023-46713

MEDIUM · 5.3 CVSS v3.1 Published 2023-12-13
Fix available
A fix is available. Upgrade to after 7.2.5 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 in Fortinet FortiWeb 6.2.0 - 6.2.8, 6.3.0 - 6.3.23, 7.0.0 - 7.0.9, 7.2.0 - 7.2.5 and 7.4.0 may allow an attacker to forge traffic logs via a crafted URL of the web application.

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 in FortiWeb where improper output neutralization allows attackers to forge traffic logs by including malicious characters in crafted URLs. An attacker could inject arbitrary content into log entries by embedding newline characters or other special characters in the URL, potentially hiding malicious activity or causing issues in log analysis systems that parse these logs.

MitigationApply the vendor patch for this vulnerability. In the interim, implement log monitoring to detect anomalous patterns in traffic logs that may indicate injection attempts.

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
FortiwebApplication
Affected:>= 6.2.0, <= 6.2.8>= 6.3.0, <= 6.3.23>= 7.0.0, <= 7.0.9>= 7.2.0, <= 7.2.5= 7.4.0

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. Check FortiWeb firmware version
    Run the command 'get system status' in the FortiWeb CLI or check System > Firmware in the GUI to view the running firmware version.
    Affected if The version falls within any of these ranges: 6.2.0 through 6.2.8, 6.3.0 through 6.3.23, 7.0.0 through 7.0.9, 7.2.0 through 7.2.5, or exactly 7.4.0.
  2. Verify traffic logging is enabled
    In the FortiWeb GUI, navigate to Log > Log Config > Traffic Log or run 'get log traffic' in the CLI to confirm traffic logging is turned on.
    Affected if Traffic logging is enabled - this is required for the log injection vulnerability to be exploitable.
  3. Inspect traffic logs for injection patterns
    Review recent traffic logs (located in Log > Traffic Log or via 'execute log traffic' command) and search for entries where the URL field contains newline characters (\n), carriage returns, or multiple entries appearing on the same line that suggest URL data was injected with special characters.
    Affected if Log entries contain URLs with embedded newlines or unusual character sequences that do not match expected URL encoding, indicating potential log injection attempts.
  4. Correlate log entries with incoming requests
    Compare suspicious log entries against the actual incoming request logs or packet captures to verify if the logged URL matches what was actually requested. Look for discrepancies where the log shows multiline entries or unexpected URL content.
    Affected if Log entries show URL content that exceeds what was transmitted in the corresponding request, or entries appear to span multiple lines unexpectedly.

You are affected if your FortiWeb version is within the listed ranges AND traffic logging is enabled AND your logs contain entries with injected newline characters or anomalous URL patterns that do not match the actual requests.

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.2.5
Interim mitigation

Apply the vendor patch for this vulnerability. In the interim, implement log monitoring to detect anomalous patterns in traffic logs that may indicate injection attempts.

Recommended fix Moderate confidence

Upgrade to the latest available version in your respective branch: 6.2.9+, 6.3.24+, 7.0.10+, 7.2.6+, or 7.4.1+ (preferably the latest stable release)

  1. 1. Identify the current FortiWeb version by navigating to the FortiWeb GUI or running 'get system status' in CLI
  2. 2. Determine which version branch your current installation belongs to (6.2.x, 6.3.x, 7.0.x, 7.2.x, or 7.4.x)
  3. 3. Access Fortinet Customer Support portal at https://support.fortinet.com/ to download the appropriate firmware upgrade
  4. 4. For FortiWeb 6.2.x: upgrade to version 6.2.9 or later
  5. 5. For FortiWeb 6.3.x: upgrade to version 6.3.24 or later
  6. 6. For FortiWeb 7.0.x: upgrade to version 7.0.10 or later
  7. 7. For FortiWeb 7.2.x: upgrade to version 7.2.6 or later
  8. 8. For FortiWeb 7.4.x: upgrade to version 7.4.1 or later
Caveat Review FortiWeb release notes for your target version for any configuration or behavioral changes; test thoroughly in non-production first as with any major firmware upgrade

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

Fix this in Fortiweb Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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