FortimanagerApplication · Fortinet
CVE-2015-3612
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 (XSS) vulnerability exists in FortiManager 5.2.1 and earlier and 5.0.10 and earlier via an unspecified parameter in the FortiWeb auto update service page.
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 confidenceCross-site Scripting (XSS) vulnerability in FortiManager versions 5.2.1 and earlier and 5.0.10 and earlier. The vulnerability exists in the FortiWeb auto update service page through an unspecified parameter that fails to properly sanitize user input, allowing injection of malicious script 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
FortimanagerApplication
>= 5.0.0, <= 5.0.10>= 5.2.0, <= 5.2.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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 FortiManager versionLog into the FortiManager CLI or GUI and navigate to the system information page, or run the command 'get system status' in the CLI to retrieve the firmware version.Affected if The version is 5.0.0 through 5.0.10, or 5.2.0 through 5.2.1.
-
Confirm FortiWeb auto update service is enabledIn the FortiManager GUI, navigate to FortiWeb > System > Service or check the FortiWeb settings page. In CLI, use 'show' commands related to web防范 configurations or check for FortiWeb integration settings.Affected if The FortiWeb auto update service or FortiWeb integration feature is configured and enabled on the system.
-
Verify web interface accessibilityCheck the FortiManager interface bindings and access permissions using 'get system interface' and 'show system admin' commands to confirm which IP addresses or networks can reach the web UI.Affected if The FortiManager web interface is accessible to untrusted users or networks, allowing them to reach the FortiWeb auto update service page.
You are affected if your FortiManager version falls within 5.0.0-5.0.10 or 5.2.0-5.2.1 AND the FortiWeb auto update service is enabled and accessible to users who could inject malicious script.
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 dataApply vendor-supplied patches for FortiManager 5.0.x to version 5.0.11 or later, and for 5.2.x to version 5.2.2 or later. Until patches are applied, consider disabling the FortiWeb auto update service or restricting access to trusted administrators only.
Fix this in Fortimanager
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-3612 — 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-2015-3612 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