dbcve.org
InjectionWeakness · CWE-74

CVE-2026-10202

MEDIUM · 6.3 CVSS v3.1 Published 2026-06-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was identified in OFCMS 1.1.3. This issue affects the function Query of the file \ofcms-admin\src\main\java\com\ofsoft\cms\admin\controller\system\SystemDictController.java of the component JSON Query Interface. The manipulation leads to sql injection. The attack can be initiated 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

SQL injection vulnerability in the Query function of SystemDictController.java in OFCMS 1.1.3's JSON Query Interface allows remote attackers to manipulate SQL queries through unsanitized input. The exploit is publicly available and can be exploited remotely without authentication.

MitigationUntil vendor patch is available, implement parameterized queries/prepared statements for the Query function and add input validation. Review and fix similar SQL query patterns across the codebase.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm OFCMS version
    Locate the version file or build configuration in the OFCMS installation (commonly version.txt, pom.xml, or the admin dashboard About section)
    Affected if The installed version is exactly 1.1.3 or falls within the 1.1.x range where this vulnerability exists
  2. Locate SystemDictController.java
    Search the source code or decompiled classes for the file SystemDictController.java, typically found under src/main/java/com/ofcms/controller/ or similar controller paths
    Affected if The file exists and contains a Query or query method handling JSON requests
  3. Verify vulnerable Query function exists
    Inspect the Query function in SystemDictController.java and look for SQL query construction that uses user-supplied parameters directly in the query string without parameterized binding (e.g., string concatenation of request parameters into SQL)
    Affected if The Query function builds SQL statements by directly concatenating user input without using PreparedStatement or similar parameterization
  4. Check JSON Query Interface exposure
    Identify the REST endpoint mapped to the Query function (typically /admin/system/dict/query or similar JSON API path) and verify it is accessible without authentication or with low-privilege user access
    Affected if The JSON Query Interface endpoint is exposed and accepts user-controlled parameters that flow into the vulnerable SQL construction
  5. Inspect runtime SQL execution patterns
    Enable database query logging or use runtime debugging to capture the actual SQL queries executed when the dict query endpoint receives crafted input
    Affected if Logged queries show unsanitized user input directly embedded in SQL syntax, confirming the injection point

A defender is affected if running OFCMS 1.1.3 with SystemDictController.java containing the unparameterized Query function that the JSON interface exposes to user-supplied input.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Until vendor patch is available, implement parameterized queries/prepared statements for the Query function and add input validation. Review and fix similar SQL query patterns across the codebase.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10202 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-10202 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data