LiveActive security incident?Get immediate response
CVE Record

CVE-2019-13346: In MyT 1.5.1, the User[username] parameter has XSS.

In MyT 1.5.1, the User[username] parameter has XSS.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2019-13346 is a reported cross-site scripting issue in MyT 1.5.1 involving the User[username] parameter. A malicious value could be interpreted by a user's browser instead of treated as plain text. The public record lacks CVSS scoring, affected CPEs, and vendor remediation details, so urgency depends on whether MyT 1.5.1 is deployed and exposed.

Executive priority

Prioritize confirmation of exposure. If MyT 1.5.1 is internet-facing or used by privileged users, treat remediation as time-sensitive. If the product is not deployed, document non-exposure and monitor for any new vendor or CVE updates.

Technical view

The CVE description states that MyT 1.5.1 has XSS in the User[username] parameter. The source bundle includes an Exploit-DB reference, but no CVSS vector, CWE assignment, vendor advisory, patch version, or detailed affected-product metadata. CISA KEV status is false, so the provided sources do not establish known active exploitation.

Likely exposure

Exposure is likely limited to environments running MyT 1.5.1, especially where user-controlled username values are rendered in web pages. The bundle does not identify CPEs, deployment model, authentication requirements, or affected components beyond the parameter name.

Exploitation context

A public Exploit-DB reference exists, indicating public exploit information is available. The provided sources do not show KEV listing, active exploitation, confirmed exploitation in the wild, or exploitation prerequisites. Treat this as a public XSS weakness with incomplete severity evidence.

Researcher notes

The record is sparse: no CVSS, CWE, CPE, patch reference, or vendor advisory appears in the bundle. Analysis is based on the CVE description and Exploit-DB reference only. Avoid assuming broader product versions, authentication state, or exploit maturity beyond those sources.

Mitigation direction

  • Check vendor or project guidance for a fixed version or official workaround.
  • Upgrade MyT if a trusted fixed release is available.
  • Restrict access to any exposed MyT 1.5.1 instance during review.
  • Ensure username output is safely encoded wherever rendered.
  • Reject or neutralize unsafe username content in application handling.

Validation and detection

  • Inventory whether MyT 1.5.1 is deployed in your environment.
  • Confirm whether the User[username] value is rendered in browser-visible pages.
  • Review logs for suspicious username changes or unexpected script-like content.
  • Use safe, non-destructive XSS testing in a controlled environment.
  • Verify any vendor update or workaround removes unsafe rendering behavior.
Prepared
Confidence
medium
Sources
3

Public sources used

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-2019-13346 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.