dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-22785

CRITICAL · 9.3 CVSS v3.1 Published 2025-01-15
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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in ComMotion Course Booking System course-booking-system allows SQL Injection.This issue affects Course Booking System: from n/a through <= 6.0.6.

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 ComMotion Course Booking System allows attackers to inject malicious SQL queries through unsanitized input in the course-booking-system component. The critical CVSS score of 9.3 suggests unauthenticated remote exploitation is possible, potentially allowing complete database compromise including exposure of sensitive booking data.

MitigationReplace all dynamic SQL queries with parameterized queries or prepared statements, implement strict input validation on all user-supplied parameters, and apply the latest available patch from the vendor.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/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 ComMotion Course Booking System is installed
    Search your application inventory, web server directories, or deployed packages for 'ComMotion' or 'course-booking-system' components. Check your software bill of materials (SBOM) if available.
    Affected if The ComMotion Course Booking System or its course-booking-system component is found in your environment
  2. Identify the installed version
    Check version files, package manifests (package.json, composer.json, etc.), or the application About/Admin panel for the ComMotion Course Booking System version number.
    Affected if You cannot determine the version OR the version falls within the affected release range (contact vendor for specific versions)
  3. Verify the course-booking-system component is exposed
    Review your web server configuration, routing tables, or API endpoints to confirm the '/course-booking-system' or booking-related endpoints are publicly accessible or enabled.
    Affected if The course-booking-system component is exposed via HTTP/HTTPS endpoints
  4. Check for input handling in booking functionality
    Inspect the application's booking submission forms and API parameters. Look for user-supplied fields (such as course ID, user details, date parameters) that are passed to database queries without obvious sanitization.
    Affected if The booking system accepts user input that flows directly into SQL queries without parameterized query usage
  5. Review application logs for suspicious SQL patterns
    Examine application and database logs for unusual SQL syntax, UNION SELECT statements, or common SQL injection payloads in booking-related request parameters.
    Affected if SQL injection payloads or anomalous SQL patterns appear in your logs for booking functionality

Your environment is affected if ComMotion Course Booking System with an exposed course-booking-system component is installed and the booking functionality handles user input without parameterized queries.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace all dynamic SQL queries with parameterized queries or prepared statements, implement strict input validation on all user-supplied parameters, and apply the latest available patch from the vendor.

Recommended fix Moderate confidence

Upgrade to a version beyond 6.0.6 (e.g., 6.0.7 or later) - verify the specific fixed release with the vendor

  1. Obtain the latest version of ComMotion Course Booking System from the official vendor or project repository
  2. Review the vendor's release notes or changelog to confirm the version includes the SQL injection fix (CVE-2025-22785)
  3. Backup the current database and application files before proceeding with the upgrade
  4. Deploy the new version following the vendor's standard upgrade procedure
  5. Verify the application functions correctly after the upgrade
  6. Confirm the vulnerability is resolved by testing or consulting the vendor's security advisory
Caveat Check vendor release notes for any breaking changes between your current version and the target version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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