CVE-2020-27726
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 · uneditedIn versions 16.0.0-16.0.0.1, 15.1.0-15.1.0.5, 14.1.0-14.1.3, 13.1.0-13.1.3.4, and 12.1.0-12.1.5.2, a reflected cross-site scripting (XSS) vulnerability exists in the resource information page for authenticated users when a full webtop is configured on the BIG-IP APM system.
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 reflected cross-site scripting (XSS) vulnerability exists in the resource information page of BIG-IP APM when a full webtop is configured. Authenticated users can inject malicious scripts through unsanitized input reflected back by the server.
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>= 12.1.0, <= 12.1.5>= 13.1.0, < 13.1.3.5>= 14.1.0, < 14.1.3.1>= 15.0.0, < 15.1.1>= 16.0.0, < 16.0.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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Verify APM module is provisionedLog into the BIG-IP management console and navigate to System > Resource Provisioning. Confirm that Access Policy Manager (APM) is provisioned and enabled.Affected if APM is not provisioned, the vulnerability does not apply since it targets APM functionality.
-
Check BIG-IP version against affected rangesRun 'tmsh show sys version' on the command line or check System > Software > ISO Image in the management UI to identify the installed version.Affected if The installed version falls within any of these ranges: 12.1.0-12.1.5, 13.1.0-13.1.3.4, 14.1.0-14.1.3.0, 15.0.0-15.1.0.x, or 16.0.0-16.0.0.x.
-
Confirm full webtop configuration existsNavigate to Access Policy > Webtops > Webtop List in the BIG-IP configuration. Review existing webtop configurations and identify whether any are configured as type 'Full'.Affected if No full webtop is configured, the specific attack surface for this CVE is not present.
-
Inspect resource information page handlingExamine APM access policy configurations that include resource information pages or landing pages for webtop resources. Look for any custom iRules or responses that handle unsanitized user input.Affected if Custom access policy or iRules reflect user-supplied input back to the browser without sanitization on resource information pages.
A user is affected if APM is provisioned, the BIG-IP version is within the affected ranges listed, AND a full webtop configuration exists that serves resource information pages handling user input.
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 data13.1.3.514.1.3.115.1.1
Upgrade to a patched BIG-IP version or implement input validation/sanitization on the resource information page to prevent script injection.
- 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-2020-27726 — 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-27726 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