Security readout for executives and security teams
Plain-English summary
OFCMS 1.1.3 has a SQL injection flaw in an administrative JSON query function. A remote authenticated attacker may be able to read, change, or disrupt database data. Public exploit information exists, but the provided sources do not show confirmed active exploitation or an official fix.
Executive priority
Treat as a near-term remediation item if OFCMS 1.1.3 is in use. Business urgency rises if the admin interface is internet-accessible or broadly available internally. Prioritize access restriction and monitoring while waiting for confirmed vendor guidance.
Technical view
The issue affects the Query function in SystemDictController.java under ofcms-admin, component JSON Query Interface. Manipulated input can reach SQL handling, classified as CWE-89 and CWE-74. CVSS v2 is 6.5 with network access, low complexity, and single authentication required. VulDB states proof-of-concept exploit availability and no vendor response yet.
Likely exposure
Exposure is likely limited to organizations running OFCMS 1.1.3, especially if the admin or JSON query interface is reachable by authenticated users over a network. Systems not using OFCMS or not on version 1.1.3 are not identified as affected in the provided sources.
Exploitation context
The sources state exploitation can be initiated remotely and that public exploit material may be available. The CVSS vector indicates authentication is required. There is no KEV listing and no cited evidence of active exploitation in the provided material.
Researcher notes
Evidence is primarily from VulDB and the CVE record. The vendor was reportedly notified through a Gitee issue but had not responded at publication. Avoid assuming affected versions beyond OFCMS 1.1.3 or claiming active exploitation without new supporting sources.
Mitigation direction
- Identify any OFCMS 1.1.3 deployments and owners.
- Restrict access to OFCMS administrative interfaces to trusted networks and users.
- Review vendor project channels for an official patch or workaround.
- Monitor database and application logs for suspicious query activity.
- Apply a vendor-supported update when one becomes available.
Validation and detection
- Confirm whether OFCMS is deployed and record its version.
- Verify whether the JSON Query Interface is reachable remotely.
- Review user access to OFCMS administrative functions.
- Check logs for unusual dictionary query errors or unexpected database access.
- Track the Gitee issue and VulDB entry for remediation updates.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-74: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-10202 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (2.0)
- Known Exploited
- No
- Published
Vector: AV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
4 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
AV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR86.4VulDBCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R2.83.4VulDBCVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R2.83.4VulDBCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P——VulDBVulnerability scoring details
Base CVSS 4.0 score
5.3MediumVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
Base CVSS 3.1 score
6.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R
Base CVSS 3.0 score
6.3MediumVector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R
Base CVSS 2.0 score
6.5MediumVector: AV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timelineVulDB
Advisory disclosed
- Source timelineVulDB
VulDB entry created
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- Source timelineVulDB
VulDB entry last update
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- VDB-367482 | OFCMS JSON Query SystemDictController.java query sql injectionCVE reference, VulDB · vdb-entry, technical-description
- VDB-367482 | CTI Indicators (IOB, IOC, TTP, IOA)CVE reference, VulDB · signature, permissions-required
- CVE-2026-10202 | CVE Analysis and ReportCVE reference, VulDB · third-party-advisory
- Submit #821181 | https://gitee.com/oufu/ofcms OFCMS v1.1.3 SQL InjectionCVE reference, VulDB · third-party-advisory
- https://gitee.com/oufu/ofcms/issues/IJLIBTCVE reference, VulDB · exploit, issue-tracking
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.