Security readout for executives and security teams
Plain-English summary
Tryton 5.4 is reported to store unsafe script content in a user's profile name. When that name is displayed in Tryton's frontend or backend interfaces, the script may run in another user's browser, creating account, data exposure, and workflow-integrity risk.
Executive priority
Treat as a moderate-priority application security issue. It is not marked as known exploited, but stored XSS can affect administrators and business workflows if an internal or compromised account can plant malicious content.
Technical view
This is a persistent cross-site scripting issue in Tryton's user profile name input, classified as CWE-79. The CVSS 3.1 vector indicates network access, low complexity, low privileges, changed scope, and low confidentiality and integrity impact, with no availability impact.
Likely exposure
Exposure is most likely in organizations running Tryton 5.4 where authenticated users can modify profile names viewed by other users or administrators. The bundle does not prove exposure for other Tryton versions.
Exploitation context
The source bundle includes public exploit and third-party advisory references, so proof-of-concept information appears public. KEV is false, and the provided sources do not establish active exploitation in the wild.
Researcher notes
Key uncertainty is remediation: the provided bundle names the vulnerability and public references but does not include a specific patch version or vendor advisory text. Avoid expanding affected versions beyond Tryton 5.4 without vendor confirmation.
Mitigation direction
- Inventory Tryton deployments and identify any running version 5.4.
- Check official Tryton guidance for fixed versions or vendor-recommended remediation.
- Upgrade or apply vendor fixes when confirmed applicable.
- Review stored profile names for script-like markup or unexpected HTML.
- Limit profile-name changes to trusted authenticated users where operationally feasible.
- Use output encoding and CSP as compensating controls, not replacements for vendor fixes.
Validation and detection
- Confirm deployed Tryton versions against the advisory scope.
- Verify whether user profile names are rendered in frontend and backend views.
- Review existing profile-name data for suspicious markup.
- Check application behavior for safe output encoding in profile-name displays.
- Review access controls for who can edit profile names.
- Document whether no vendor fix was identified in the provided sources.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2020-37014 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
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.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N3.12.7VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
5.1MediumVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N
Base CVSS 3.1 score
6.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- ExploitDB-48466CVE reference, VulnCheck · exploit
- Official Tryton HomepageCVE reference, VulnCheck · product
- Tryton Download PageCVE reference, VulnCheck · product
- Vulnerability Lab AdvisoryCVE reference, VulnCheck · third-party-advisory
- VulnCheck Advisory: Tryton 5.4 - Persistent Cross-Site ScriptingCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.