Security readout for executives and security teams
Plain-English summary
CVE-2022-31456 is a medium-severity cross-site scripting issue in Truedesk v1.2.2. An attacker can place malicious web content in a team name, which may run when another user views it. Business impact is mainly account trust, session exposure, and unauthorized UI actions, not direct server takeover.
Executive priority
Treat as a scheduled remediation item unless Truedesk is internet-facing, handles sensitive support data, or has many privileged users. Prioritize higher if administrators routinely view user-controlled team data.
Technical view
The CVE describes XSS through the Truedesk v1.2.2 team name parameter. CVSS 3.1 score is 6.1: network exploitable, low complexity, no privileges required, but user interaction is required. Scope is changed with low confidentiality and integrity impact, and no availability impact.
Likely exposure
Organizations running Truedesk v1.2.2 are the stated exposure group. The bundle does not provide vendor, CPE, deployment prevalence, or affected-version range beyond v1.2.2.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation evidence. Exploitation appears to require getting a user to view attacker-controlled team name content in the application.
Researcher notes
Evidence is limited to the CVE description, CVSS vector, KEV=false status, and public references. No official patch version, commit, CWE, CPE, or exploitation confirmation is included in the provided bundle.
Mitigation direction
- Check Truedesk vendor guidance for a fixed release or official workaround.
- Upgrade away from Truedesk v1.2.2 if a maintained fixed version exists.
- Encode team names on output and sanitize untrusted HTML input.
- Restrict team-management access until remediation is confirmed.
- Use Content Security Policy as defense-in-depth against XSS impact.
Validation and detection
- Inventory Truedesk instances and confirm whether v1.2.2 is deployed.
- Review team name rendering for output encoding and HTML sanitization.
- Test in staging with a safe non-executing XSS marker.
- Check logs for unexpected team name changes or suspicious HTML content.
- Confirm remediation with regression tests covering team name display paths.
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.
CVE-2022-31456 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.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
CVSS vector scores
1 official scoreWe 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:N/UI:R/S:C/C:L/I:L/A:N2.82.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.1MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.acunetix.com/vulnerabilities/web/cross-site-scripting/CVE reference
- https://medium.com/%40rohitgautam26/cve-2022-31456-c8bbefba6cc1CVE reference
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.
