Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-65103: CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in devcode-it openstamanager

0
High
VulnerabilityCVE-2025-65103cvecve-2025-65103cwe-89
Published: Wed Nov 19 2025 (11/19/2025, 19:09:09 UTC)
Source: CVE Database V5
Vendor/Project: devcode-it
Product: openstamanager

Description

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.

AI-Powered Analysis

AILast updated: 11/26/2025, 20:03:09 UTC

Technical Analysis

CVE-2025-65103 is an authenticated SQL Injection vulnerability identified in the OpenSTAManager software developed by devcode-it, affecting all versions prior to 2.9.5. OpenSTAManager is an open-source management platform used primarily for technical assistance and invoicing, often deployed by small and medium enterprises (SMEs). The vulnerability arises from improper neutralization of special elements in SQL commands (CWE-89), specifically through the 'display' parameter in API requests. An attacker with any level of authentication can manipulate this parameter to inject arbitrary SQL queries. This flaw enables attackers to exfiltrate sensitive data, modify records, or delete database content, potentially leading to full system compromise including unauthorized access to business-critical data and disruption of invoicing and technical support operations. The vulnerability has a CVSS 3.1 base score of 8.8, reflecting high confidentiality, integrity, and availability impacts, with network attack vector, low attack complexity, and requiring only low privileges but no user interaction. Although no exploits have been reported in the wild yet, the vulnerability's nature and ease of exploitation make it a significant risk. The issue was addressed and patched in OpenSTAManager version 2.9.5, which sanitizes input properly to prevent SQL injection. Organizations running vulnerable versions should prioritize upgrading to mitigate risk.

Potential Impact

For European organizations, especially SMEs relying on OpenSTAManager for managing technical assistance and invoicing, this vulnerability poses a critical risk. Exploitation can lead to unauthorized disclosure of sensitive customer and financial data, manipulation or deletion of invoicing records, and disruption of business operations. This can result in financial losses, regulatory non-compliance (e.g., GDPR violations due to data breaches), reputational damage, and operational downtime. Since the vulnerability allows any authenticated user to perform SQL injection, insider threats or compromised credentials can be leveraged to escalate attacks. The availability impact could disrupt invoicing and support services, affecting customer trust and revenue streams. Given the widespread use of open-source management tools in European SMEs, the threat could have broad implications if not mitigated promptly.

Mitigation Recommendations

1. Immediately upgrade OpenSTAManager installations to version 2.9.5 or later, where the vulnerability is patched. 2. Restrict API access strictly to trusted and authenticated users, implementing strong authentication mechanisms such as multi-factor authentication (MFA). 3. Conduct a thorough audit of user permissions to ensure least privilege principles are enforced, minimizing the number of users with API access. 4. Monitor API logs for unusual or suspicious queries, especially those manipulating the 'display' parameter or exhibiting anomalous SQL patterns. 5. Implement Web Application Firewalls (WAFs) with rules designed to detect and block SQL injection attempts targeting the API endpoints. 6. Regularly back up databases and verify backup integrity to enable recovery in case of data tampering or deletion. 7. Educate users and administrators about the risks of SQL injection and the importance of applying security patches promptly. 8. Consider network segmentation to isolate critical management systems from broader corporate networks to limit lateral movement in case of compromise.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2025-11-17T20:55:34.693Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 691e18af49ba98bd8186a296

Added to database: 11/19/2025, 7:21:19 PM

Last enriched: 11/26/2025, 8:03:09 PM

Last updated: 1/7/2026, 4:53:17 AM

Views: 56

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats