CVE-2026-100880 zhistaredu CVE debrief

Who should care

Defenders responsible for zhistaredu StarTraining systems should assess exposure and prioritize verification of inventory and potential impact. They should also consider applying patches or mitigations if available and review compensating controls for exposed systems while remediation is scheduled and verified.

Why it matters

Defenders should prioritize verifying the presence of this vulnerability in their inventory and assessing the potential impact on their systems.

• Verify the presence of this vulnerability in your inventory
• Assess the potential impact on your systems
• Consider applying patches or mitigations if available

Technical summary

A weakness has been identified in zhistaredu StarTraining up to 3.8.1. This vulnerability affects unknown code of the file du-common/src/main/java/com/edu/common/utils/file/MimeTypeUtils.java of the component Upload Endpoint. This manipulation of the argument File causes cross site scripting. It is possible to initiate the attack remotely. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way. Defenders should prioritize verifying the presence of this vulnerability in their inventory and assessing the potential impact on their systems.

Defensive priority

Defenders should prioritize verifying the presence of this vulnerability in their inventory and assessing the potential impact on their systems.

Recommended defensive actions

• Verify the presence of this vulnerability in your inventory
• Assess the potential impact on your systems
• Consider applying patches or mitigations if available
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide limited information about the vulnerability. The exploit has been made available to the public, but there is no information on actual attacks or victims. Defenders should verify the presence of this vulnerability in their inventory and assess the potential impact on their systems with explicit evidence-limit language and defensive verification tasks. Limited source detail is available, so defenders should proceed with caution and consider applying patches or mitigations if available.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.