LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1062: xiweicheng TMS HtmlUtil.java summary server-side request forgery

A flaw has been found in xiweicheng TMS up to 2.28.0. This affects the function Summary of the file src/main/java/com/lhjz/portal/util/HtmlUtil.java. This manipulation of the argument url causes server-side request forgery. It is possible to initiate the attack remotely. The exploit has been published and may be used.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-1062 is a server-side request forgery issue in xiweicheng TMS up to 2.28.0. A logged-in remote attacker may be able to make the TMS server request attacker-chosen URLs. Business risk depends on whether TMS can reach internal services, cloud metadata, or sensitive network locations.

Executive priority

Treat as a near-term risk review item, not an emergency based on current evidence. Prioritize if TMS is internet-accessible, widely user-accessible, or hosted in networks with sensitive internal services reachable from the application server.

Technical view

VulDB describes SSRF in the Summary function of src/main/java/com/lhjz/portal/util/HtmlUtil.java, caused by manipulation of the url argument. The CVSS v2 score is 6.5 with network access, low complexity, and authentication required. Public proof-of-concept material is referenced, but the CVE is not listed as KEV in the provided bundle.

Likely exposure

Organizations running xiweicheng TMS versions 2.0 through 2.28.0 are in scope. Exposure is higher where authenticated users can reach the affected function and the server has outbound access to internal or sensitive resources.

Exploitation context

The source bundle says the attack can be initiated remotely and that exploit material has been published. It does not show confirmed active exploitation. Authentication is required according to the CVSS vector and VulDB indicator reference.

Researcher notes

Evidence is centered on VulDB and linked public reports. The affected range is broad, but the bundle does not name a vendor patch, commit, or workaround. Avoid assuming compromise from exploit publication alone; validate authentication requirements and network reachability in the local deployment.

Mitigation direction

  • Check xiweicheng or project guidance for fixed versions or official mitigations.
  • Restrict TMS server outbound network access to required destinations only.
  • Apply strict allowlisting for URL-fetching features where configurable.
  • Block access from TMS to metadata, loopback, and internal administrative services.
  • Review user access to affected TMS functions and remove unnecessary accounts.

Validation and detection

  • Inventory xiweicheng TMS deployments and confirm versions.
  • Identify any instances running 2.0 through 2.28.0.
  • Review code or configuration around HtmlUtil.java Summary URL handling.
  • Check application logs for unusual server-initiated URL requests.
  • Confirm outbound egress controls from TMS servers are enforced.
Prepared
Confidence
medium
Sources
8

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.

cwe · medium confidence lookup

CWE-918: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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 lookup
description · low confidence lookup

Cloud metadata behavior lookup

The CVE wording references SSRF or metadata access, so cloud discovery and credential material 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-2026-1062 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
Medium
CVSS
6.5 (2.0)
Known Exploited
No
Published

Vector: AV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR

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.

1CVSS vectors
0Timeline events
0ADP providers
7Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 2.0MediumAV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR86.4Primary CVE score

Vulnerability scoring details

Base CVSS 2.0 score

6.5Medium
CVSS 2.0 vector shape for CVE-2026-1062Access VectorAccess ComplexityAuthenticationConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: AV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR

Access Vector
NetworkAdjacentLocal
Access Complexity
LowMediumHigh
Authentication
NoneSingleMultiple
Confidentiality Impact
CompletePartialNone
Integrity Impact
CompletePartialNone
Availability Impact
CompletePartialNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
xiweichengTMS2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6, 2.7, 2.8, 2.9, 2.10, 2.11, 2.12, 2.13, 2.14, 2.15, 2.16, 2.17, 2.18, 2.19, 2.20, 2.21, 2.22, 2.23, 2.24, 2.25, 2.26, 2.27, 2.28.0Listed
Weakness

CWE details

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

CWE-918 · source CWE mapping

Server-Side Request Forgery (SSRF)

Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.