dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-10692

HIGH · 7.1 CVSS v4.0 Published 2025-10-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
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
The endpoint POST /api/staff/get-new-tickets concatenates the user-controlled parameter departmentId directly into the SQL WHERE clause without parameter binding. As a result, an authenticated staff user (level ≥ 1) can inject SQL to alter the filter logic, effectively bypassing department scoping and disclosing tickets beyond their intended access.This issue affects OpenSupports: 4.11.0.

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

SQL injection vulnerability in OpenSupports 4.11.0 where the POST /api/staff/get-new-tickets endpoint concatenates the user-controlled departmentId parameter directly into a SQL WHERE clause without parameter binding. An authenticated staff user with privilege level ≥1 can inject malicious SQL to bypass department scoping and access tickets outside their authorized scope.

MitigationReplace direct string concatenation with parameterized queries/prepared statements for the departmentId parameter. Implement proper input validation and enforce least-privilege access controls for staff roles.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 OpenSupports installation and version
    Locate the OpenSupports installation directory and check the version file (often in config files, package.json, or the main application file). Run: grep -r 'version' or check the admin dashboard for the installed version.
    Affected if Installed version is 4.11.0 (the only version specified as affected)
  2. Verify the staff API endpoint exists
    Check if the route /api/staff/get-new-tickets is defined in the application's routing configuration (typically in routes/api.php, routes/index.js, or similar routing files).
    Affected if The endpoint is present and accessible in the application routing
  3. Confirm staff authentication is enabled
    Inspect the authentication configuration for staff users. Check if session-based or token-based auth is configured for staff in config/auth.php, config/session.php, or similar config files.
    Affected if Staff authentication is enabled and users with privilege level ≥1 can authenticate
  4. Identify department scoping configuration
    Review the staff user permissions or role configuration to determine if department assignment is enforced. Look for department_id fields in staff user tables or configuration files.
    Affected if Staff users are assigned to specific departments and department scoping is meant to restrict ticket access
  5. Locate the vulnerable endpoint handler
    Find the server-side code handling POST /api/staff/get-new-tickets. Search for the departmentId parameter usage in the controller or route handler. Look for direct SQL query construction without parameterized binding.
    Affected if The code uses direct string concatenation for departmentId in the SQL WHERE clause (e.g., "WHERE department_id = " + departmentId)

A user is affected if they run OpenSupports version 4.11.0, the staff API endpoint exists, staff authentication is enabled, and the departmentId parameter is concatenated directly into SQL queries without prepared statements.

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

Replace direct string concatenation with parameterized queries/prepared statements for the departmentId parameter. Implement proper input validation and enforce least-privilege access controls for staff roles.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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