CVE-2026-1062
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA server-side request forgery (SSRF) vulnerability exists in xiweicheng TMS up to version 2.28.0 in the Summary function of HtmlUtil.java. The function accepts a user-controlled URL parameter and makes server-side requests to it without proper validation, allowing attackers to abuse the server to scan internal resources or access cloud metadata services.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2.28.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed version of Xiweicheng TMSLocate the application version information - check the about page, config files, or the war/jar manifest. Compare the version number against the affected range (<= 2.28.0)Affected if The installed version is 2.28.0 or lower
-
Locate the HtmlUtil.java componentSearch the application codebase or deployed files for HtmlUtil.java and verify the Summary function existsAffected if The file exists with the Summary function present in the application
-
Verify the Summary endpoint is accessibleIdentify if there is an HTTP endpoint that invokes the Summary function in HtmlUtil.java - typically this would be a web request that triggers URL fetching functionalityAffected if The Summary endpoint is exposed and reachable without authentication or with low-privileged user access
-
Check for user-controlled URL parametersReview the application requests that invoke the Summary function - look for parameters that accept URLs and are passed to server-side request operationsAffected if The application accepts arbitrary URLs from user input and uses them in server-side HTTP requests
-
Inspect access logs for SSRF indicatorsReview application and web server logs for requests to internal IP ranges (127.0.0.1, 10.x.x.x, 192.168.x.x), cloud metadata endpoints (169.254.169.254), or unusual outbound patterns from the Summary functionalityAffected if Logs show requests to internal resources or metadata services originating from the server
You are affected if Xiweicheng TMS version is 2.28.0 or lower AND the Summary function in HtmlUtil.java is accessible, allowing user-supplied URLs to trigger server-side requests.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict URL allowlist validation to restrict accessible domains/IPs, disable the ability to fetch arbitrary URLs if not business-critical, and upgrade to a patched version when available.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1062 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-1062 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data