CVE-2025-10969
Blind SQL Injection in Farktor E-Commerce Package Through
Publication date: 2026-02-12
Last updated on: 2026-03-10
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 |
|---|---|---|
| farktor | e-commerce_package | to 2025-11-27 (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 in the Farktor Software E-Commerce Package. Specifically, it is a Blind SQL Injection caused by improper neutralization of special elements used in SQL commands. This means that an attacker can manipulate the SQL queries executed by the application by injecting malicious SQL code, potentially without immediate visible feedback.
How can this vulnerability impact me? :
The impact of this vulnerability is severe, as indicated by its high CVSS score of 9.8. An attacker can exploit this Blind SQL Injection to gain unauthorized access to sensitive data, modify or delete data, and disrupt the availability of the affected system. This can lead to data breaches, loss of data integrity, and denial of service.
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