FortianalyzerApplication · Fortinet
CVE-2020-12815
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 improper neutralization of input vulnerability in FortiTester before 3.9.0 may allow a remote authenticated attacker to inject script related HTML tags via IPv4/IPv6 address fields.
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 confidenceA stored cross-site scripting (XSS) vulnerability in FortiTester before version 3.9.0 allows authenticated attackers to inject malicious HTML/script tags through IPv4/IPv6 address input fields. When other users view or interact with the affected fields, the injected scripts execute in their browser context.
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
FortianalyzerApplication
<= 6.2.5>= 6.4.0, <= 6.4.1
FortitesterApplication
<= 3.7.0= 3.8.0CVSS 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 FortiTester versionAccess FortiTester GUI, go to System > Settings > Firmware, or use CLI command 'get system status' to retrieve the installed versionAffected if Version is 3.8.0, or any version 3.7.0 or lower (versions below 3.9.0)
-
Identify FortiAnalyzer version if integratedCheck FortiAnalyzer version via GUI under System > Settings > Firmware, or use CLI 'get system status' on the FortiAnalyzer deviceAffected if FortiAnalyzer version is 6.2.5 or lower, or between 6.4.0 and 6.4.1 inclusive
-
Verify IPv4/IPv6 address input fields existNavigate to FortiTester interface areas that accept IP address input, such as network settings, test configuration, or device management sections. Look for fields labeled for IPv4 or IPv6 addressesAffected if These IPv4/IPv6 address input fields are present and accessible in the interface
-
Confirm authentication access to the interfaceVerify that user accounts exist with access to the FortiTester web interface where IP address fields are exposedAffected if Authenticated users can access the interface containing IPv4/IPv6 address input fields
You are affected if FortiTester version is 3.8.0 or below 3.9.0 (or FortiAnalyzer is 6.2.5 or lower/6.4.0-6.4.1) AND authenticated users can access IPv4/IPv6 address input fields in the interface.
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 FortiTester to version 3.9.0 or later, which includes proper input validation and output encoding for IPv4/IPv6 address fields.
Fix this in Fortianalyzer
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-12815 — 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-2020-12815 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