dbcve.org
FortiproxyApplication · Fortinet

CVE-2019-15706

MEDIUM · 5.4 CVSS v3.1 Published 2025-03-17
Fix available
A fix is available. Upgrade to 5.6.13 / 6.0.9 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 input during web page generation in the SSL VPN portal of FortiProxy version 2.0.0, version 1.2.9 and below and FortiOS version 6.2.1 and below, version 6.0.8 and below, version 5.6.12 may allow a remote authenticated attacker to perform a stored cross site scripting attack (XSS).

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 stored cross-site scripting (XSS) vulnerability exists in the SSL VPN portal of FortiProxy and FortiOS. An authenticated remote attacker can inject malicious JavaScript code that gets stored on the server and executed in the browsers of other users viewing the VPN portal pages.

MitigationApply the vendor-supplied patches/updates for FortiOS or FortiProxy to address the input validation flaw. Alternatively, restrict SSL VPN access to trusted users and implement Content Security Policy (CSP) headers as a defense-in-depth measure.

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
FortiproxyApplication
Affected:>= 1.2.0, <= 1.2.9= 2.0.0
FortiosOperating system
Affected:>= 5.6.0, < 5.6.13>= 6.0.0, < 6.0.9>= 6.2.0, < 6.2.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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/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 Fortinet product
    Run the command 'get system status' or 'diagnose system version' on the FortiGate CLI to determine if the device is FortiOS or FortiProxy
    Affected if The device is not FortiOS or FortiProxy (the CVE only applies to these products)
  2. Check the FortiOS version
    Run 'get system status' in the CLI and locate the 'FortiOS' version field
    Affected if The version matches any of these ranges: 5.6.0 to 5.6.12, 6.0.0 to 6.0.8, or 6.2.0 to 6.2.1
  3. Check the FortiProxy version
    Run 'get system status' in the CLI and locate the 'FortiProxy' version field
    Affected if The version is 1.2.0 to 1.2.9, or exactly 2.0.0
  4. Verify SSL VPN portal is configured
    In the GUI, navigate to VPN > SSL-VPN Settings, or run 'show vpn ssl settings' in the CLI to check if SSL VPN portal is enabled
    Affected if SSL VPN portal is enabled and accessible to users (the XSS requires this feature to be active for injection and execution)

The device is affected if it runs FortiOS within versions 5.6.0-5.6.12, 6.0.0-6.0.8, or 6.2.0-6.2.1, OR FortiProxy versions 1.2.0-1.2.9 or 2.0.0, AND the SSL VPN portal feature is enabled.

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 5.6.13 / 6.0.9 / 6.2.2 or later
Fixed in 5.6.136.0.96.2.2
Interim mitigation

Apply the vendor-supplied patches/updates for FortiOS or FortiProxy to address the input validation flaw. Alternatively, restrict SSL VPN access to trusted users and implement Content Security Policy (CSP) headers as a defense-in-depth measure.

Recommended fix High confidence

FortiOS: 5.6.13, 6.0.9, or 6.2.2 and later; FortiProxy: 2.0.1 or later

  1. Identify the current FortiOS or FortiProxy version by checking System > Firmware or running 'get system status' in CLI
  2. Determine if the version is affected: FortiOS 5.6.0-5.6.12, 6.0.0-6.0.8, 6.2.0-6.2.1, or FortiProxy 1.2.0-1.2.9, 2.0.0
  3. Schedule a maintenance window for the upgrade
  4. Obtain the appropriate firmware from Fortinet support portal (support.fortinet.com)
  5. Backup the current configuration using 'execute backup full-config' or via GUI
  6. Upload and install the fixed firmware version: FortiOS 5.6.13 or later, 6.0.9 or later, 6.2.2 or later; FortiProxy 2.0.1 or later
  7. Verify the upgrade was successful and the version is correct
  8. Confirm the XSS vulnerability is resolved by checking the SSL VPN portal functionality
Caveat Review Fortinet release notes for the target version for any configuration or feature changes that may require adjustment

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

Fix this in Fortiproxy Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
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,488.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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