dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-65103

HIGH · 8.8 CVSS v3.1 Published 2025-11-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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
OpenSTAManager is an open source management software for technical assistance and invoicing. Prior to version 2.9.5, an authenticated SQL Injection vulnerability in the API allows any user, regardless of permission level, to execute arbitrary SQL queries. By manipulating the display parameter in an API request, an attacker can exfiltrate, modify, or delete any data in the database, leading to a full system compromise. This issue has been patched in version 2.9.5.

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

OpenSTAManager prior to version 2.9.5 contains an authenticated SQL Injection vulnerability in its API. The display parameter in API requests is not properly sanitized, allowing any authenticated user—even those with no elevated permissions—to inject arbitrary SQL queries. This enables data exfiltration, modification, deletion, and potentially full database/system compromise.

MitigationUpgrade OpenSTAManager to version 2.9.5 or later. As an immediate workaround, restrict API access to trusted users only until the upgrade can be applied.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 OpenSTAManager installation
    Locate the OpenSTAManager application directory or check for its web service running on the server. Common paths include /var/www/html/ or C:\inetpub\ on Windows servers.
    Affected if OpenSTAManager is present in the environment
  2. Determine installed version
    Check the version file or dashboard within OpenSTAManager. Typical locations include a version.php file in the root directory, or the admin dashboard showing the software version.
    Affected if The version is lower than 2.9.5 (e.g., 2.9.4, 2.9.3, earlier versions)
  3. Verify API module is accessible
    Confirm that the API endpoint is reachable. Test by accessing a known API route such as /api/ or checking if API requests return valid responses.
    Affected if API endpoints are accessible and respond to requests
  4. Confirm authenticated user accounts exist
    Check for any active user accounts in the OpenSTAManager system. This can be done by reviewing the user management section or checking the database users table.
    Affected if There is at least one authenticated user account (any privilege level)
  5. Inspect API request handling for the display parameter
    Review API code or intercept API requests to observe how the 'display' parameter is processed. Check if user-supplied input in this parameter is passed directly to SQL queries without sanitization.
    Affected if The display parameter accepts user input and is used in database queries without prepared statements or escaping

A user is affected if OpenSTAManager version is below 2.9.5, the API is accessible, and any authenticated user account exists, allowing SQL injection via the display parameter.

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

Upgrade OpenSTAManager to version 2.9.5 or later. As an immediate workaround, restrict API access to trusted users only until the upgrade can be applied.

Recommended fix High confidence

2.9.5

  1. 1. Back up your current OpenSTAManager database and files.
  2. 2. Download OpenSTAManager version 2.9.5 from the official GitHub repository.
  3. 3. Replace the existing installation files with the new version.
  4. 4. Verify the API endpoint now correctly handles the display parameter with proper parameterization.
  5. 5. Test that authenticated users can still access the API without SQL injection vulnerabilities.
  6. 6. Confirm the upgrade was successful by checking the version number in the application.

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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