CVE-2020-36902
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 · uneditedUBICOD Medivision Digital Signage 1.5.1 contains an authorization bypass vulnerability that allows normal users to escalate privileges by manipulating the 'ft[grp]' parameter. Attackers can send a GET request to /html/user with 'ft[grp]' set to integer value '3' to gain super admin rights without authentication.
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 confidenceUBICOD Medivision Digital Signage 1.5.1 contains an authorization bypass vulnerability where normal users can escalate privileges to super admin by sending a GET request to /html/user with the 'ft[grp]' parameter set to integer value '3', bypassing authentication entirely.
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= 1.5.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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 if Medivision Digital Signage is runningAccess the web interface of the system (typically on ports 80 or 443) and look for Medivision Digital Signage login page or branding. Use a browser or curl to make an HTTP request to the root URL.Affected if The Medivision Digital Signage web interface is accessible and responds to requests.
-
Determine the installed firmware versionCheck the login page, footer, or admin panel for a version number. Alternatively, check the HTTP response headers or any /about/version endpoint if available. Compare this version to 1.5.1.Affected if The installed version is exactly 1.5.1.
-
Verify the /html/user endpoint is accessibleSend a GET request to /html/user (e.g., curl -k https://TARGET/html/user or http://TARGET/html/user). Confirm the endpoint responds without being blocked by network ACLs.Affected if The /html/user endpoint returns an HTTP response (200, 401, or similar) rather than a connection error or 404.
-
Test for privilege escalation via ft[grp] parameterSend a GET request to /html/user?ft[grp]=3 (e.g., curl -k 'https://TARGET/html/user?ft[grp]=3'). Observe if the response grants super admin access or returns admin functionality without authentication.Affected if The request succeeds in bypassing authentication and grants elevated (super admin) privileges when ft[grp] is set to 3.
You are affected if Medivision Digital Signage version 1.5.1 is running and the /html/user endpoint is accessible, allowing an unauthenticated user to escalate privileges by setting the ft[grp] parameter to 3.
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 patch or update to a fixed version; if unavailable, restrict network access to /html/user endpoint and implement proper server-side authorization validation for the 'ft[grp]' parameter.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-36902 — 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-36902 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