LiveActive security incident?Get immediate response
CVE Record

CVE-2020-17476: Mibew Messenger before 3.2.7 allows XSS via a crafted user name.

Mibew Messenger before 3.2.7 allows XSS via a crafted user name.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Mibew Messenger versions before 3.2.7 allowed cross-site scripting through a crafted user name. In plain terms, attacker-controlled text could execute script in another user’s browser when the application displayed that name. The supplied sources do not show active exploitation, CVSS scoring, or business-specific impact.

Executive priority

Treat as a targeted web application hygiene issue. Prioritize if Mibew Messenger is public-facing or used by support staff handling sensitive customer conversations.

Technical view

CVE-2020-17476 is an XSS issue in Mibew Messenger before 3.2.7 involving crafted user name input. The public references identify the 3.2.7 release and a related code commit. The bundle does not specify XSS type, authentication requirements, browser context, or exact vulnerable rendering path.

Likely exposure

Exposure is most likely where Mibew Messenger before 3.2.7 is deployed, especially internet-facing chat installations accepting user-supplied names.

Exploitation context

The bundle contains no KEV listing and no cited evidence of exploitation in the wild. Exploitability details are limited to crafted user name XSS.

Researcher notes

Evidence is sparse: no CVSS, CWE, CPE, exploit status, or detailed vulnerable code path is supplied. Analysis should remain limited to Mibew Messenger before 3.2.7 and XSS via crafted user name.

Mitigation direction

  • Identify any Mibew Messenger deployments and their exact versions.
  • Upgrade Mibew Messenger to 3.2.7 or later per vendor guidance.
  • Review vendor release notes and the referenced commit before applying changes.
  • Restrict access to exposed chat administration surfaces where feasible.

Validation and detection

  • Check deployed Mibew Messenger version numbers against the before-3.2.7 affected range.
  • Confirm the 3.2.7 or later update is applied in production.
  • Review application logs for suspicious user names or script-like input.
  • Verify security scanners no longer flag CVE-2020-17476.
Prepared
Confidence
medium
Sources
4

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.

cve · low confidence lookup

CVE-2020-17476 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
3Source links

CVSS and timeline data

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

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.