FortiwebApplication · Fortinet
CVE-2014-3115
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 · uneditedMultiple cross-site request forgery (CSRF) vulnerabilities in the web administration console in Fortinet FortiWeb before 5.2.0 allow remote attackers to hijack the authentication of administrators via system/config/adminadd and other unspecified vectors.
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 confidenceMultiple CSRF vulnerabilities in Fortinet FortiWeb web administration console before version 5.2.0 allow remote attackers to hijack administrator authentication by tricking authenticated admins into submitting malicious requests, specifically via the system/config/adminadd endpoint and other unspecified vectors.
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.1.4= 5.1.0= 5.1.1= 5.1.2= 5.1.3CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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 versionLog into the FortiWeb web console or CLI and navigate to System > Status or run the command 'get system status' to view the firmware versionAffected if The version displayed is 5.1.0, 5.1.1, 5.1.2, 5.1.3, or any version 5.1.4 or lower (versions prior to 5.2.0 are affected)
-
Verify web admin console is enabledCheck if the FortiWeb web administration interface is accessible by navigating to the management IP/hostname on HTTPS port or checking the HTTP service status in Network > Interface settingsAffected if The web admin console is enabled and exposed, making CSRF attacks possible against authenticated administrators
-
Check for admin user configuration accessIn the web console, navigate to System > Admin > Administrators or use the CLI command 'show system admin' to view admin user configurationAffected if The system/config/adminadd endpoint exists and is accessible to authenticated administrators, indicating the specific CSRF vector is present
-
Confirm active admin sessions existReview System > Admin > Administrator Sessions or use 'diagnose system admin session list' to see active admin loginsAffected if There are active or recent administrator sessions on the web console, which would be required for a CSRF attack to hijack
Your environment is affected if FortiWeb version is 5.1.0 through 5.1.4 (any version below 5.2.0) and the web administration console is enabled and accessible to administrators.
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 version 5.2.0 or later to obtain the vendor patch; as an interim control, enforce strict admin session policies and educate administrators about avoiding clickable links from untrusted sources while logged into the admin console.
Fix this in Fortiweb
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-3115 — 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-2014-3115 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