dbcve.org
UjcmsApplication

CVE-2026-2954

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 found in Dromara UJCMS 10.0.2. Impacted is the function importChanel of the file /api/backend/ext/import-data/import-channel of the component ImportDataController. Performing a manipulation of the argument driverClassName/url results in injection. It is possible to initiate the attack remotely. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.

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 · high confidence

Dromara UJCMS 10.0.2 contains an injection vulnerability in the ImportDataController's importChanel function at /api/backend/ext/import-data/import-channel. The driverClassName and url parameters are not properly validated before being used to establish database connections, allowing attackers to manipulate JDBC connection parameters remotely without authentication.

MitigationImplement strict input validation on driverClassName and url parameters, restrict the import functionality to authenticated administrators only, or disable the endpoint until a vendor patch is available. Consider implementing a WAF rule to block suspicious JDBC parameter injection attempts.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
UjcmsApplication
Affected:= 10.0.2

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Identify UJCMS installation and version
    Locate the UJCMS application installation directory or check the deployed WAR/JAR file. Look for version identifiers in build configuration files (pom.xml, build.gradle), manifest files, or version properties files typically named version.properties or found in WEB-INF/classes.
    Affected if The installed UJCMS version is exactly 10.0.2
  2. Confirm the ImportDataController component exists
    Inspect the deployed application JAR or WAR file. Navigate to the compiled classpath and locate the ImportDataController class, typically found under com.ujcms.*.controller or similar package structure. Verify the importChanel method exists within this controller.
    Affected if The ImportDataController class with importChanel method is present in the deployment
  3. Check if vulnerable endpoint is exposed
    Review the application's request routing configuration or web.xml to confirm the endpoint /api/backend/ext/import-data/import-channel is mapped and accessible. If the application is running, attempt a HEAD or OPTIONS request to this endpoint to verify it responds.
    Affected if The endpoint /api/backend/ext/import-data/import-channel is registered and accessible without authentication restrictions
  4. Verify the import-channel functionality is enabled
    Check application configuration files (application.yml, application.properties) for any flags that enable or disable the import-data module, such as ujcms.import.enabled or similar properties. Also inspect if the controller has any conditional annotations that might disable it.
    Affected if The import-data module is enabled and the ImportDataController is not disabled via configuration

Your environment is affected if UJCMS version 10.0.2 is running AND the /api/backend/ext/import-data/import-channel endpoint is accessible and enabled, allowing controllable driverClassName and url parameters.

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

Implement strict input validation on driverClassName and url parameters, restrict the import functionality to authenticated administrators only, or disable the endpoint until a vendor patch is available. Consider implementing a WAF rule to block suspicious JDBC parameter injection attempts.

Fix this in Ujcms Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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