CVE-2021-36172
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 restriction of XML external entity reference vulnerability in the parser of XML responses of FortiPortal before 6.0.6 may allow an attacker who controls the producer of XML reports consumed by FortiPortal to trigger a denial of service or read arbitrary files from the underlying file system by means of specifically crafted XML documents.
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 confidenceThis is an XML External Entity (XXE) injection vulnerability in FortiPortal's XML response parser. An attacker who can control the XML content produced and consumed by FortiPortal can embed malicious external entity references in XML documents. This allows the parser to read arbitrary files from the server's filesystem or cause denial of service by triggering resource exhaustion through recursive entity expansion.
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.0.0, <= 4.0.4>= 4.1.0, <= 4.1.2>= 4.2.0, <= 4.2.4>= 5.0.0, <= 5.0.3>= 5.1.0, <= 5.1.2>= 5.2.0, <= 5.2.6>= 5.3.0, < 5.3.7>= 6.0.0, < 6.0.6CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 FortiPortal versionLocate the installed FortiPortal version through the administrative interface or system files. Check the /opt/fortiportal or similar installation directory for version information, or access the FortiPortal GUI System Settings > About page.Affected if The installed version falls within these ranges: 4.0.0 to 4.0.4, 4.1.0 to 4.1.2, 4.2.0 to 4.2.4, 5.0.0 to 5.0.3, 5.1.0 to 5.1.2, 5.2.0 to 5.2.6, 5.3.0 to 5.3.6, or 6.0.0 to 6.0.5.
-
Determine if XML content is processedIdentify if FortiPortal is configured to import, parse, or generate XML documents. Review XML-based report configurations, data import settings, or any third-party integrations that feed XML data into FortiPortal.Affected if FortiPortal processes XML documents from untrusted or attacker-controlled sources.
-
Inspect XML parser configurationExamine FortiPortal configuration files for XML parser settings. Look for parser configuration related to external entity processing, typically in XML processing or data import configuration files.Affected if The XML parser has external entity processing enabled or not explicitly disabled.
-
Audit XML data sourcesReview all systems and integrations that provide XML content to FortiPortal. Verify whether any of these sources could be influenced or controlled by an attacker.Affected if XML data originates from untrusted or potentially compromised sources.
You are affected if FortiPortal is running any version from 4.0.0 to 6.0.5 and processes XML content from sources that could be controlled by an attacker.
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.
dbcve · scoped5.3.76.0.6
Upgrade FortiPortal to version 6.0.6 or later, and ensure that XML parsers are configured to disable external entity processing. Verify that any third-party or integrated systems producing XML reports for FortiPortal are trusted and not subject to attacker control.
6.0.6
- 1. Back up the current FortiPortal configuration and data before initiating the upgrade.
- 2. Review FortiPortal upgrade documentation for your current version to ensure compatibility with version 6.0.6.
- 3. Download FortiPortal version 6.0.6 from the Fortinet Customer Support portal (https://support.fortinet.com).
- 4. Stop all FortiPortal services prior to upgrade.
- 5. Execute the upgrade installer for FortiPortal 6.0.6, following the official upgrade procedure for your deployment mode (standalone or cluster).
- 6. Verify the upgrade completed successfully by checking the FortiPortal version in the administrative interface.
- 7. Validate that FortiPortal services are running correctly and XML report processing functions normally.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-36172 — 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-2021-36172 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