FortiwebApplication · Fortinet
CVE-2017-3129
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 · uneditedA Cross-Site Scripting vulnerability in Fortinet FortiWeb versions 5.7.1 and below allows attacker to execute unauthorized code or commands via an improperly sanitized POST parameter in the FortiWeb Site Publisher feature.
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 · moderate confidenceA stored Cross-Site Scripting vulnerability exists in Fortinet FortiWeb versions 5.7.1 and below. The Site Publisher feature fails to properly sanitize a POST parameter, allowing attackers to inject malicious JavaScript or HTML that executes in the context of other users' sessions.
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
<= 5.7.1CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify FortiWeb installationLocate the FortiWeb appliance or VM in your environment. Confirm it is actively running FortiWeb as a WAF product.Affected if FortiWeb is deployed as your web application firewall solution.
-
Determine the FortiWeb versionAccess the FortiWeb CLI and run the command 'get system status' or access the GUI via System > FortiView > Dashboard to view the current firmware version.Affected if The installed version number is 5.7.1 or lower (for example, 5.7.1, 5.7.0, 5.6.x, or earlier).
-
Verify Site Publisher feature is in useLog into the FortiWeb GUI and navigate to the Site Publisher configuration section, or check the CLI output for site publish profiles using 'show web-protection profile site-publish' or related commands.Affected if Site Publisher profiles are configured and active for publishing protected web applications.
-
Inspect Site Publisher POST parameter handlingReview the Site Publisher profile configuration for any custom POST parameters that accept user input. Use FortiWeb's traffic logs or Web Application Security testing to examine how these parameters handle special characters.Affected if The Site Publisher accepts user-supplied POST parameters without visible input validation or encoding in the configuration.
If FortiWeb version 5.7.1 or lower is running with the Site Publisher feature configured, the environment is potentially affected by this stored XSS vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade FortiWeb to a version higher than 5.7.1, or implement input validation and output encoding on the Site Publisher POST parameter to neutralize malicious script payloads.
Fix this in Fortiweb
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-3129 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-3129 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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