CVE-2025-5319
SQL Injection in Emit Efficiency Management System Allows Data Access
Publication date: 2026-02-03
Last updated on: 2026-02-04
Assigner: Computer Emergency Response Team of the Republic of Turkey
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| emit_information_and_communication_technologies_industry_and_trade_ltd_co | efficiency_management_system | to 03022026 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is an SQL Injection issue found in the Efficiency Management System by Emit Information and Communication Technologies Industry and Trade Ltd. Co. It occurs due to improper neutralization of special elements used in SQL commands, allowing an attacker to manipulate the system's database queries.
How can this vulnerability impact me? :
The vulnerability has a high severity score (CVSS 9.8) and can lead to complete compromise of confidentiality, integrity, and availability of the affected system. An attacker could execute arbitrary SQL commands, potentially accessing, modifying, or deleting sensitive data without authorization.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know