dbcve.org
FortiwlcApplication · Fortinet

CVE-2017-7335

MEDIUM · 5.4 CVSS v3.0 Published 2017-10-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
A Cross-Site Scripting (XSS) vulnerability in Fortinet FortiWLC 6.1-x (6.1-2, 6.1-4 and 6.1-5); 7.0-x (7.0-7, 7.0-8, 7.0-9, 7.0-10); and 8.x (8.0, 8.1, 8.2 and 8.3.0-8.3.2) allows an authenticated user to inject arbitrary web script or HTML via non-sanitized parameters "refresh" and "branchtotable" present in HTTP POST 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

Cross-Site Scripting (XSS) vulnerability in Fortinet FortiWLC allows authenticated users to inject arbitrary web script or HTML via non-sanitized 'refresh' and 'branchtotable' parameters in HTTP POST requests to the web management interface.

MitigationImplement proper input validation and output encoding on the 'refresh' and 'branchtotable' parameters in the affected HTTP POST handlers, or apply vendor-supplied patches for affected versions (6.1-x, 7.0-x, 8.x).

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
FortiwlcApplication
Affected:= 6.1-2= 6.1-4= 6.1-5= 7.0-7= 7.0-8= 7.0-9= 7.0-10= 8.0= 8.1= 8.2= 8.3.0= 8.3.1

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.0/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 FortiWLC version
    Log into the FortiWLC web management interface or CLI and locate the firmware/version information, typically found in the System > General or About section
    Affected if The installed version is 6.1-2, 6.1-4, 6.1-5, 7.0-7, 7.0-8, 7.0-9, 7.0-10, 8.0, 8.1, 8.2, 8.3.0, or 8.3.1
  2. Confirm web management interface is enabled
    Verify that the FortiWLC web management interface (HTTP/HTTPS) is accessible and not disabled in the system configuration
    Affected if Web management interface is enabled and reachable
  3. Identify exposed POST endpoints
    Inspect HTTP traffic or review web server configuration to identify endpoints that accept POST requests with 'refresh' or 'branchtotable' parameters
    Affected if Endpoints accepting 'refresh' or 'branchtotable' parameters in POST requests exist and are accessible
  4. Verify authentication requirement
    Confirm that accessing the vulnerable endpoints requires valid authentication credentials
    Affected if The vulnerable parameters are processed after authentication without sanitization

Your environment is affected if you are running one of the listed versions with the web management interface enabled and the 'refresh' or 'branchtotable' POST parameters are processed without input validation.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and output encoding on the 'refresh' and 'branchtotable' parameters in the affected HTTP POST handlers, or apply vendor-supplied patches for affected versions (6.1-x, 7.0-x, 8.x).

Fix this in Fortiwlc Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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