CVE-2019-15710
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 · uneditedAn OS command injection vulnerability in FortiExtender 4.1.0 to 4.1.1, 4.0.0 and below under CLI admin console may allow unauthorized administrators to run arbitrary system level commands via specially crafted "execute date" commands.
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 confidenceOS command injection vulnerability in FortiExtender CLI allows authenticated administrators to execute arbitrary system commands via specially crafted 'execute date' commands. The vulnerability affects versions 4.0.0 and below through 4.1.1, enabling privilege escalation to system-level execution.
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<= 4.1.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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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 FortiExtender firmware versionAccess the FortiExtender CLI or web interface and run 'get system status' or check System > Firmware in the GUI to retrieve the installed firmware versionAffected if The installed version is 4.1.1 or below, including all 4.0.x versions and earlier releases
-
Confirm CLI access is enabledCheck the FortiExtender configuration for CLI access settings - typically under System > Administration or via 'show system interface' in CLI to verify the CLI management interface is accessibleAffected if CLI interface is exposed and accessible to administrators
-
Review administrator accounts with CLI privilegesUse 'get system admin' or view Admin Administrators in the GUI to list all accounts with administrative CLI accessAffected if There are administrator accounts configured with CLI access, particularly untrusted or unexpected accounts
-
Inspect CLI command logs for suspicious execute date usageCheck FortiExtender logs for 'execute date' commands - look in Log & Report > Event Log or use 'execute log filter' in CLI to search for command execution history involving the 'execute date' parameterAffected if There are logged 'execute date' commands that appear unusual, malformed, or contain unexpected parameters that could indicate exploitation attempts
A FortiExtender device is affected if it runs firmware version 4.1.1 or below, has CLI access enabled, and has administrator accounts that could potentially execute the vulnerable 'execute date' command sequence.
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 FortiExtender to version 4.1.2 or later. Additionally, restrict CLI access to trusted administrators only and implement least-privilege administrative accounts.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15710 — 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-2019-15710 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