Vulnerability in java110 MicroCommunity (CVE-2026-96803)
Summary
Vulnerability in java110 MicroCommunity (CVE-2026-96803). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
A vulnerability was identified in java110 MicroCommunity up to 2.0. Affected is the function QueryServiceSMOImpl.fallBack of the file BusinessApi.java of the component fallBack API Endpoint. Such manipulation of the argument fallBackSql leads to sql injection. The attack may be launched remotely. The exploit is publicly available and might be used. The project was informed of the problem early through an issue report but has not responded yet.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-96803 has been found in java110 MicroCommunity.
Risk of unauthorized operations or information disclosure. CVSS score: 7.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "java110 MicroCommunity CVE-2026-96803" on the vendor's site.
CVE-2026-96803 (java110 MicroCommunity) — CWE-74 / CVSS v3 7.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-74) exists in java110 MicroCommunity.
Check the vendor advisory for the affected versions of java110 MicroCommunity.
Severity: High (CVSS 7.3/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで java110 MicroCommunity を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web gitee.com
- web vuldb.com
- web vuldb.com
- web vuldb.com
- web vuldb.com
- web nvd.nist.gov
- web github.com