LiveActive security incident?Get immediate response
CVE Record

CVE-2020-28149: myDBR 5.8.3/4262 is affected by: Cross Site Scripting (XSS).

myDBR 5.8.3/4262 is affected by: Cross Site Scripting (XSS). The impact is: execute arbitrary code (remote). The component is: CSRF Token. The attack vector is: CSRF token injection to XSS.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-28149 describes a cross-site scripting issue in myDBR 5.8.3/4262 involving CSRF token handling. If reachable, it could let an attacker run script in a victim's browser context. The source bundle does not provide CVSS, confirmed fixes, or active exploitation evidence.

Executive priority

Set priority after inventory. If myDBR 5.8.3/4262 is internet-facing or used by privileged staff, treat remediation as time-sensitive. If no affected build exists, record non-exposure and monitor vendor information.

Technical view

The CVE states that myDBR 5.8.3/4262 has XSS via CSRF token injection. The affected metadata is incomplete, with vendor/product listed as n/a and no CWE or CVSS. Treat the technical scope as limited to the named myDBR build unless vendor guidance expands it.

Likely exposure

Exposure is most likely where myDBR 5.8.3/4262 is deployed and accessible to users who can be targeted through web interactions. The bundle does not establish whether authentication is required or whether other versions are affected.

Exploitation context

The CVE source describes an XSS attack vector but provides no KEV listing and no cited evidence of active exploitation. A public reference exists, but the supplied bundle does not include exploit maturity, prevalence, or patch status.

Researcher notes

Evidence is sparse. The CVE names myDBR 5.8.3/4262 and a CSRF-token-to-XSS path, but omits CVSS, CWE, CPE, vendor fix details, and exploitation confirmation. Avoid broad version claims without vendor corroboration.

Mitigation direction

  • Inventory myDBR deployments and identify any 5.8.3/4262 instances.
  • Check myDBR vendor guidance for a fixed release or supported workaround.
  • Reduce external access to affected myDBR instances where feasible.
  • Prioritize standard XSS defenses around token output encoding and input handling.
  • Monitor for suspicious web requests involving CSRF token parameters.

Validation and detection

  • Confirm installed myDBR version and build number on each instance.
  • Review whether CSRF token values are reflected into browser-rendered contexts.
  • Run only authorized, non-destructive XSS validation in test environments.
  • Check logs for unusual CSRF token parameter activity.
  • Document whether each instance is internet-facing, internal, or retired.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-28149 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.