dbcve.org
InjectionWeakness · CWE-74

CVE-2026-10204

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 weakness has been identified in OFCMS 1.1.3. The affected element is the function Query of the file \ofcms-admin\src\main\java\com\ofsoft\cms\admin\controller\system\SysUserController.java of the component JSON Query Interface. This manipulation causes sql injection. The attack may be initiated remotely. The exploit has been made available to the public and could be used for attacks. 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 OFCMS 1.1.3 within the JSON Query Interface of SysUserController.java. The Query function fails to properly sanitize user input, allowing remote attackers to inject malicious SQL statements through the affected endpoint.

MitigationUpgrade to a patched version of OFCMS once available, or implement parameterized queries/prepared statements in the Query function of SysUserController.java to properly sanitize SQL input.

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 installation
    Locate OFCMS by checking web server directories (e.g., Apache Tomcat webapps, JBoss, or similar) for OFCMS artifacts such as the ofcms directory or ofcms.war file. Alternatively, check for OFCMS banners or identifying files in the application root.
    Affected if OFCMS is present on the system
  2. Verify OFCMS version
    Check the installed OFCMS version by examining version files (such as version.properties, version.json, or similar), the admin dashboard footer, or by querying the system information page if available. Compare the found version against the affected version 1.1.3.
    Affected if The installed version is 1.1.3 or falls within an affected version range for this CVE
  3. Identify SysUserController.java accessibility
    Determine if the SysUserController component is deployed and accessible. This is typically found in the compiled classes under the path related to SysUserController. Check if the application's JSON query endpoint is exposed (often accessible via URLs containing /json/ or similar API patterns).
    Affected if The SysUserController is deployed and the JSON Query Interface is accessible over the network
  4. Check if Query function is exposed
    Inspect the application's URL routing to determine if the Query function within SysUserController is reachable. This typically involves checking if endpoints related to user query functionality are accessible without authentication or accessible to the attacking user role.
    Affected if The Query function endpoint is exposed and reachable without proper authentication or authorization controls
  5. Inspect input handling in Query function
    If code inspection is possible, examine the SysUserController.java Query function for direct use of user-supplied parameters in SQL statements without parameterized queries or input sanitization. If black-box testing, attempt benign SQL injection payloads in query parameters to verify the vulnerability exists.
    Affected if User-supplied input is used directly in SQL queries without sanitization or parameterized queries

A system is affected if it runs OFCMS version 1.1.3 (or an affected version) with the SysUserController Query function and JSON Query Interface exposed and accessible, where user input flows directly into SQL queries without sanitization.

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

Upgrade to a patched version of OFCMS once available, or implement parameterized queries/prepared statements in the Query function of SysUserController.java to properly sanitize SQL input.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10204 — 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-10204 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