Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach exposed fallBack API endpoint
-
ExploitInject SQL via fallBackSql argument
-
ExecutionQuery executes attacker SQL in database
-
ImpactExfiltrate or modify stored data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires network reachability to the MicroCommunity fallBack API endpoint (BusinessApi.java → QueryServiceSMOImpl.fallBack) and the ability to control the fallBackSql request argument, which is interpolated into a SQL query. VulDB rates this PR:N (no authentication), so exploitation is claimed against a reachable instance without credentials; however this is not independently confirmed and the endpoint may in practice sit behind application authentication, which would limit real-world exposure. Limiting factors: the product is a niche self-hosted platform, no fixed/patched version exists yet, and exploitation depends on the instance being network-accessible to the attacker. |
| Impact | The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N, base 6.9) describes a network-reachable, low-complexity SQL injection requiring no privileges or user interaction, with the E:P (Proof-of-Concept) exploit-maturity flag matching the publicly posted Gitee exploit. Signals are mostly consistent - a public POC exists and the attack vector is remote - but there is no CISA KEV listing and no EPSS score in the input, so there is no evidence of active or automated exploitation; this is 'publicly available exploit code exists,' not confirmed in-the-wild abuse. The vendor's own impact rating (VC:L/VI:L/VA:L) is notably conservative for a raw SQL-injection primitive: an endpoint literally named fallBack that consumes an argument called fallBackSql suggests near-direct SQL execution, which typically yields full database read and often write, i.e. C:H/I:H rather than only 'low' impacts - VulDB frequently under-scores impact this way. The main uncertainty is authentication: the description and vendor vector assert PR:N (unauthenticated), but a fallback/query administrative endpoint on a management platform plausibly sits behind a login, which would raise the real-world bar. Net: a genuine, easily-triggered injection with public POC, but confined to a niche product, so priority is moderate and driven by whoever actually exposes MicroCommunity to untrusted networks. |
| Exploit ScenarioDerived | A remote attacker sends a crafted request to the MicroCommunity fallBack API endpoint (BusinessApi.java), placing malicious SQL in the fallBackSql parameter that is concatenated into a database query executed by QueryServiceSMOImpl.fallBack. Because the attack vector is network-based with low complexity, the attacker extracts or manipulates database contents (user records, credentials, community/property data). A public exploit is already available via the Gitee issue tracker, lowering the skill required. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 24, 2026
SQL injection in java110 MicroCommunity (through version 2.0) allows remote attackers to inject arbitrary SQL through the fallBackSql argument of the fallBack API endpoint implemented in BusinessApi.java / QueryServiceSMOImpl.fallBack. Publicly available exploit code exists (published as a Gitee issue), and because CVSS 4.0 carries PR:N, exploitation is claimed to need no authentication - though an independent assessment notes the endpoint may in practice sit behind application authentication, which would narrow real-world exposure. The project has not responded to the report, so no vendor fix is identified, and the CVE is not listed in CISA KEV, meaning confirmed active exploitation has not been established.
RemediationAI
No vendor-released patch identified at time of analysis: the project was informed via the Gitee issue (https://gitee.com/yhx070424/MicroCommunity/issues/IK4014) but has not responded, and VulDB (https://vuldb.com/vuln/409035) records no fixed version, so compensating controls are required. Highest-value action is to stop the endpoint being reachable: block or restrict access to the fallBack API path at the reverse proxy/WAF so only trusted management networks can call it - the trade-off is that any legitimate fallback functionality relying on that route stops working for outside callers. If the route is not needed, remove or comment out the fallBack mapping/handler in BusinessApi.java and redeploy - this eliminates the attack surface but breaks dependent features until an upstream fix lands. Where the endpoint must stay exposed, apply WAF/input validation rules rejecting SQL metacharacters and keywords in fallBackSql, accepting that encoded or obfuscated payloads can bypass signature-based filters. Additionally, run the MicroCommunity database connection under a least-privilege account with no DDL or cross-schema read rights to cap what a successful injection can reach, and monitor application logs for malformed SQL or repeated errors from the fallBack endpoint as a detection signal. Upgrade as soon as an upstream fixed release is published, since all versions up to 2.0 are currently affected.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-89, SQL injection, in the Java-based java110 MicroCommunity community/property management platform. The fallBack routine of QueryServiceSMOImpl receives the fallBackSql request argument from the fallBack API endpoint (BusinessApi.java) and interpolates it into a SQL statement rather than binding it as a parameter, letting attacker-controlled text alter query structure. The 'fallBack' naming suggests a secondary/error-recovery query path in a service-oriented (SMO) data layer, a common place for ad hoc query strings to bypass the parameterization used elsewhere. The CPE cpe:2.3:a:java110:microcommunity:*:*:*:*:*:*:*:* with a wildcard version indicates every released version (up to and including 2.0 per the report) is treated as affected, since no fixed release exists. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N, VC:L/VI:L/VA:L, E:P) scores the flaw 6.9 with only limited confidentiality/integrity impact, whereas the independent assessment (CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N) treats a successful injection on a reachable instance as full loss of confidentiality and integrity; neither model finds availability impact.
Know when Microcommunity gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
Remote low-complexity SQL injection via fallBackSql with no auth claimed (PR:N); an injectable SQL primitive typically yields full DB read/write, so C:H/I:H, A:N.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
Lifecycle Timeline
2DescriptionCVE.org
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.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
EUVD-2026-85776
GHSA-4mm4-mwxf-r2wr
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB