PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-108775 erzhongxmu CVE debrief

A vulnerability was found in erzhongxmu JEEWMS up to 2026.09.27-W39 in the Search Endpoint, specifically in the WvNoticeController.list function of the WvNoticeController.java file. The manipulation of the searchstr argument leads to SQL injection. Remote exploitation of the attack is possible. The exploit has been disclosed to the public and may be used.

Vendor
erzhongxmu
Product
JEEWMS
CVSS
LOW 2.1
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-12
Original CVE updated
2026-10-12
Advisory published
2026-10-12
Advisory updated
2026-10-12

Who should care

Defenders responsible for JEEWMS installations, especially those using version 2026.09.27-W39 or earlier, should assess the exposure of their systems to SQL injection attacks through the Search Endpoint.

Why it matters

This vulnerability allows for remote SQL injection attacks through the Search Endpoint in JEEWMS installations using version 2026.09.27-W39 or earlier. Defenders should prioritize verifying the presence of this vulnerability, assessing exposure, and implementing necessary controls.

  • Verify the presence of this vulnerability in JEEWMS installations.
  • Assess the feasibility of SQL injection attacks through the Search Endpoint.
  • Implement input validation and sanitization for the searchstr argument.
  • Monitor for potential exploitation attempts.

Technical summary

The vulnerability is located in the WvNoticeController.list function of the WvNoticeController.java file in the JEEWMS application. The searchstr argument is not properly sanitized, allowing for SQL injection attacks. This vulnerability allows for remote SQL injection attacks through the Search Endpoint in JEEWMS installations using version 2026.09.27-W39 or earlier. Defenders should prioritize verifying the presence of this vulnerability, assessing exposure, and implementing necessary controls. The manipulation of  

Defensive priority

Defenders should prioritize verifying the presence of this vulnerability in their JEEWMS installations, especially if the version 2026.09.27-W39 or earlier is in use, and assess the feasibility of SQL injection attacks through the Search Endpoint.

Recommended defensive actions

  • Verify the version of JEEWMS in use and check if it is 2026.09.27-W39 or earlier.
  • Assess the exposure of the Search Endpoint to SQL injection attacks.
  • Implement input validation and sanitization for the searchstr argument.
  • Monitor for potential exploitation attempts.
  • 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.

Evidence notes

The CVE Program record and NVD vulnerability detail provide official information about the vulnerability. Additional details are available from supplemental sources, including VulDB entries. Defenders should verify the presence of this vulnerability in JEEWMS installations, especially if the version 2026.09.27-W39 or earlier is in use, and assess the feasibility of SQL injection attacks through the Search Endpoint. The searchstr argument is not properly sanitized, allowing for SQL injection attacks. The exploit has been disclosed to  

Sources and references

Verified primary and authoritative sources

  • CVE-2026-108775 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-108775

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-108775 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-108775

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

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