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-22214: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

0
Medium
VulnerabilityCVE-2025-22214cvecve-2025-22214cwe-89
Published: Thu Jan 02 2025 (01/02/2025, 00:00:00 UTC)
Source: CVE Database V5

Description

CVE-2025-22214 is a medium severity SQL injection vulnerability affecting Landray EIS versions 2001 through 2006. The flaw exists in the Message/fi_message_receiver. aspx? replyid= parameter, which does not properly neutralize special elements used in SQL commands, allowing an attacker with low privileges to inject SQL code. Exploitation does not require user interaction and can lead to limited confidentiality impact without affecting integrity or availability. No known exploits are currently reported in the wild, and no patches have been published yet. Organizations using affected Landray EIS versions should prioritize input validation and consider compensating controls to mitigate risk. Countries with significant deployments of Landray EIS, particularly China and regions with Chinese enterprise software usage, are most at risk. Due to the medium CVSS score and limited impact scope, the vulnerability should be addressed promptly but is not critical.

AI-Powered Analysis

AILast updated: 02/25/2026, 22:10:50 UTC

Technical Analysis

CVE-2025-22214 is an SQL injection vulnerability classified under CWE-89, found in the Landray EIS enterprise information system versions 2001 through 2006. The vulnerability resides in the Message/fi_message_receiver.aspx endpoint, specifically in the 'replyid' parameter, which fails to properly sanitize or neutralize special characters used in SQL commands. This improper neutralization allows an attacker with low privileges to inject malicious SQL statements into the backend database query. The vulnerability does not require user interaction and can be exploited remotely over the network. According to the CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N), the attack complexity is low, privileges required are low, and there is no need for user interaction. The impact is limited to confidentiality, potentially allowing attackers to read some data from the database but not modify or delete it, nor disrupt service availability. No known exploits have been reported in the wild, and no official patches or mitigations have been published yet. Given the affected versions span a wide range of Landray EIS releases, organizations using these legacy systems are at risk if exposed to untrusted networks. The vulnerability highlights the importance of input validation and secure coding practices in web applications handling database queries.

Potential Impact

The primary impact of CVE-2025-22214 is a limited confidentiality breach, where an attacker can extract sensitive information from the backend database by injecting crafted SQL commands. Although the vulnerability does not allow modification or deletion of data (integrity) or disruption of service (availability), unauthorized data disclosure can lead to information leakage, privacy violations, and potential reconnaissance for further attacks. Organizations relying on Landray EIS versions 2001-2006, especially those exposing the vulnerable endpoint to external or untrusted networks, face increased risk of data exposure. The medium CVSS score reflects the moderate severity due to limited impact scope and the requirement for low privileges. However, the lack of patches and the legacy nature of the software may prolong exposure. Attackers could leverage this vulnerability to gain insights into internal data structures or user information, which could be used in subsequent targeted attacks or social engineering campaigns.

Mitigation Recommendations

To mitigate CVE-2025-22214, organizations should first assess whether they are running affected versions of Landray EIS (2001 through 2006) and identify if the vulnerable endpoint Message/fi_message_receiver.aspx is accessible. Since no official patches are currently available, immediate mitigations include implementing strict input validation and sanitization on the 'replyid' parameter to neutralize special SQL characters. Employing web application firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting this endpoint can provide an additional layer of defense. Network segmentation and restricting access to the application from trusted IP ranges can reduce exposure. Monitoring application logs for suspicious query patterns or repeated failed attempts to inject SQL code is recommended to detect potential exploitation attempts. Long-term mitigation involves upgrading to a supported and patched version of Landray EIS or migrating to alternative enterprise systems with secure coding practices. Security teams should also conduct regular code reviews and penetration testing focused on injection vulnerabilities.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
mitre
Date Reserved
2025-01-02T00:00:00.000Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6b1bb7ef31ef0b54e2e7

Added to database: 2/25/2026, 9:35:23 PM

Last enriched: 2/25/2026, 10:10:50 PM

Last updated: 2/26/2026, 6:51:21 AM

Views: 1

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