CVE-2025-11343
BaseFortify
Publication date: 2025-10-06
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| code-projects | crud_operation_system | to 3.3 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
| 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?
CVE-2025-11343 is a critical SQL injection vulnerability in version 3.3 of the Student Crud Operation project by code-projects, specifically in the delete.php file. The vulnerability occurs because the 'id' parameter is improperly handled and directly concatenated into SQL commands without proper validation or neutralization. This allows remote attackers to inject arbitrary SQL code, potentially executing unauthorized database commands without authentication. [1, 2]
How can this vulnerability impact me? :
This vulnerability can severely impact the integrity and availability of your database. An attacker can remotely execute arbitrary SQL commands, such as deleting all records in a table, leading to data loss or corruption. Since no authentication is required, the attack can be carried out easily, compromising the affected system's reliability and data integrity. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by searching for the presence of the vulnerable script delete.php with the id parameter exposed. One method is using Google dorking with the query "inurl:delete.php" to identify potentially vulnerable targets. Additionally, testing the delete.php endpoint by injecting SQL payloads into the id parameter (e.g., appending " OR 1=1 -- ") can reveal if SQL injection is possible. Network monitoring tools can also be used to detect suspicious requests targeting delete.php with unusual id parameter values. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to safely handle the id parameter (e.g., using mysqli->prepare and bind_param("i", id)). Validate the id parameter to ensure it is an integer before processing. Enforce authentication and authorization checks to restrict access to the delete operation. If possible, replace the affected component with an alternative product or updated version that addresses this vulnerability. [2, 1]