CVE-2026-10193
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 · uneditedA security flaw has been discovered in OFCMS up to 1.1.3. The impacted element is the function Query of the file ofcms-admin\src\main\java\com\ofsoft\cms\admin\controller\ComnController.java of the component ComnController. Performing a manipulation of the argument system.user.query results in sql injection. The attack may be initiated remotely. The exploit has been released to the public and may 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 confidenceSQL injection vulnerability in OFCMS admin panel's ComnController component. The Query function in ComnController.java accepts unsanitized user input through the system.user.query parameter, allowing remote attackers to inject malicious SQL statements and potentially extract or manipulate database contents.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify OFCMS installation and versionLocate the OFCMS deployment and check for version indicators such as version files, pom.xml, or application metadata. Common locations include the web root directory or WEB-INF folder. Compare the found version against the affected range (up to 1.1.3).Affected if OFCMS version is 1.1.3 or lower, or the version cannot be determined but OFCMS is present.
-
Verify ComnController component existsLocate the ComnController.java file within the deployed application source or decompiled classes. Check for the presence of a Query function/method within this controller.Affected if The ComnController.java file with a Query function exists in the OFCMS deployment.
-
Check if Query endpoint is accessibleExamine the web application routing configuration or the ComnController mappings to determine if the Query function is exposed via an HTTP endpoint (typically under a path like /system/user/query or similar).Affected if The Query function is mapped to a publicly or internally accessible HTTP route.
-
Confirm authentication statusReview the application's security configuration to determine whether authentication is required and enforced for accessing the Query endpoint. Check if default admin credentials are in use or if authentication can be bypassed.Affected if Authentication is disabled, uses default credentials, or can be bypassed, allowing unauthorized access to the vulnerable endpoint.
The environment is affected if OFCMS version 1.1.3 or lower is deployed, the ComnController Query function is accessible, and the system.user.query parameter is processed without parameterized queries.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement prepared statements/parameterized queries to sanitize the system.user.query parameter input, and restrict admin panel access to authorized users only until an official patch is released.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2026-10193 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-10193 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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