SQL Injection
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
How It Works
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements. When developers concatenate untrusted data into queries without proper sanitization, attackers can inject SQL syntax that changes the query's logic. For example, entering ' OR '1'='1 into a login form might transform SELECT * FROM users WHERE username='input' into a query that always returns true, bypassing authentication.
Attackers follow a methodical process: first probing input fields with special characters like quotes or semicolons to trigger database errors, then identifying whether the application is vulnerable. Once confirmed, they escalate by injecting commands to extract data (UNION-based attacks to merge results from other tables), manipulate records, or probe the database structure. Blind SQL injection variants work without visible error messages—boolean-based attacks infer data by observing application behavior changes, while time-based attacks use database sleep functions to confirm successful injection through response delays.
Advanced scenarios include second-order injection, where malicious input is stored in the database and later executed in a different context, and out-of-band attacks that exfiltrate data through DNS queries or HTTP requests when direct data retrieval isn't possible. Some database systems enable attackers to execute operating system commands through built-in functions like MySQL's LOAD_FILE or SQL Server's xp_cmdshell, escalating from database compromise to full server control.
Impact
- Complete data breach — extraction of entire database contents including credentials, personal information, and proprietary data
- Authentication bypass — logging in as any user without knowing passwords
- Data manipulation — unauthorized modification or deletion of critical records
- Privilege escalation — granting administrative rights to attacker-controlled accounts
- Remote code execution — leveraging database features to run operating system commands and compromise the underlying server
- Lateral movement — using compromised database credentials to access other connected systems
Real-World Examples
FreePBX's CVE-2025-66039 demonstrated a complete attack chain where SQL injection across 11 parameters in four different endpoints allowed attackers to write malicious entries into the cron_jobs table. When the system's scheduler executed these entries, the injected SQL transformed into operating system commands, granting full server control. The vulnerability required no authentication, making it immediately exploitable.
E-commerce platforms have suffered massive breaches through shopping cart SQL injection, where attackers inserted skimming code into stored procedures that executed during checkout, harvesting credit card data from thousands of transactions. Healthcare systems have been compromised through patient portal vulnerabilities, exposing millions of medical records when attackers injected UNION queries to merge data from supposedly isolated tables.
Mitigation
- Parameterized queries (prepared statements) — separates SQL logic from data, making injection syntactically impossible
- Object-Relational Mapping (ORM) frameworks — abstracts database interactions with built-in protections when used correctly
- Strict input validation — whitelist acceptable characters and formats, reject suspicious patterns
- Least privilege database accounts — applications should use credentials with minimal necessary permissions
- Web Application Firewall (WAF) — detects and blocks common injection patterns as a secondary defense layer
- Database activity monitoring — alerts on unusual query patterns or privilege escalation attempts
Recent CVEs (16090)
SQL injection in code-projects Payroll Management System 1.0 via the ID parameter in /ajax.php?action=save_department allows remote attackers to execute arbitrary SQL commands, potentially compromising backend database content. A public proof-of-concept exploit is available, but no active exploitation has been confirmed (EPSS 0.06%).
SQL injection in Inventory Management System 1.0 allows remote attackers to execute arbitrary SQL commands via the editProductName parameter in /php_action/editProduct.php. A public proof-of-concept exploit exists, but no active exploitation has been confirmed. The vulnerability has a medium CVSS 4.0 score and low EPSS likelihood, indicating limited practical risk outside of exposed installations.
SQL injection in code-projects Inventory Management System 1.0 allows remote attackers to execute arbitrary SQL commands via the productId parameter in /php_action/removeProduct.php. An unauthenticated attacker can potentially access or modify database contents, though impact is rated low. A public proof-of-concept exists, but EPSS indicates low exploitation probability.
SQL injection in code-projects Inventory Management System 1.0 allows remote attackers to manipulate database queries via the /php_action/createOrder.php endpoint. Exploit code is publicly available, but no active exploitation has been confirmed. The issue affects a niche open-source project with limited real-world deployment, resulting in low overall risk despite easy exploitability.
SQL injection in code-projects Inventory Management System 1.0 allows remote unauthenticated attackers to interfere with database queries via the productName parameter in /php_action/createProduct.php. Exploit code is publicly available, though the EPSS score of 0.06% indicates a low probability of widespread exploitation at this time.
SQL injection in code-projects Inventory Management System 1.0 allows remote attackers to manipulate the brandId parameter in removeBrand.php, potentially leading to unauthorized data access or modification. Exploit code is publicly available but no active exploitation has been confirmed, and EPSS risk is low.
SQL injection in code-projects Food Distributor Site 1.0 allows remote attackers to bypass authentication or extract sensitive data via crafted username/password inputs at /admin/process_login.php. A public proof-of-concept exploit is available, but no active exploitation has been confirmed. Despite being classified as "critical" by the reporter, the CVSS 4.0 base score is 5.5 (Medium) with low impact across confidentiality, integrity, and availability.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Mavi Yeşil Software Guest Tracking Software allows SQL Injection.This issue affects Guest Tracking Software. NOTE: The vendor did not inform about the completion of the fixing process within the specified time. The CVE will be updated when new information becomes available.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Eron Software Wowwo CRM allows Blind SQL Injection.This issue affects Wowwo CRM. NOTE: The vendor did not inform about the completion of the fixing process within the specified time. The CVE will be updated when new information becomes available.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Mobilteg Mobile Informatics Mikro Hand Terminal - MikroDB allows SQL Injection.This issue affects Mikro Hand Terminal - MikroDB. NOTE: The vendor did not inform about the completion of the fixing process within the specified time. The CVE will be updated when new information becomes available.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Case Informatics Case ERP allows SQL Injection.This issue affects Case ERP: before V2.0.1.
WeGIA is an open source web manager with a focus on the Portuguese language and charitable institutions. A Time-Based Blind SQL Injection vulnerability was discovered in version 3.3.3 the almox parameter of the `/controle/getProdutosPorAlmox.php` endpoint. This issue allows any unauthenticated attacker to inject arbitrary SQL queries, potentially leading to unauthorized data access or further exploitation depending on database configuration. Version 3.4.0 fixes the issue.
SQL injection in the findAllHosByCondition method of sfturing hosp_order allows a remote authenticated attacker to manipulate the hospitalName parameter to execute arbitrary SQL commands. The vulnerability affects the project up to commit 627f426331da8086ce8fff2017d65b1ddef384f8 and has publicly available exploit code, but it requires low-privilege authentication and has a low CVSS 4.0 score of 2.1 due to limited impact. No versioned patch exists because the project uses continuous delivery, but the issue is tracked in the GitHub repository.
SQL injection via Cross-Site Request Forgery in the sh1zen WP Optimizer WordPress plugin (all versions through 2.3.6) lets a remote attacker who lures a logged-in privileged user into visiting a malicious page forge a state-changing request that reaches an unsanitized SQL query. Rated CVSS 9.6 with a scope change, it can compromise the WordPress database, but exploitation hinges on user interaction and there is no public exploit and a negligible EPSS of 0.03%.
Authenticated SQL injection exists in the WP Forum Server WordPress plugin up to version 1.8.2, enabling high-privileged attackers (administrators) to read arbitrary data from the database. Exploitation requires administrative access and results in high confidentiality impact; no active exploitation or public exploit is known, and EPSS indicates a very low probability of widespread use.
Authenticated SQL injection in the Wow-Company Hover Effects plugin for WordPress up to version 2.1.2 allows high-privilege attackers to extract sensitive information from the website database. The vulnerability requires administrative access to the plugin interface, but successful exploitation can fully compromise data confidentiality. No active exploitation or public exploit code has been identified at the time of analysis.
High-privilege SQL injection in the YaySMTP WordPress plugin (versions through 2.6.5) allows authenticated administrators to extract sensitive database information via network requests. No active exploitation or public exploit code has been identified, and EPSS predicts a low 0.05% chance of exploitation in the near term.
SQL injection in the findDoctorByCondition function of sfturing hosp_order allows authenticated remote attackers to execute arbitrary SQL commands via the hospitalName parameter. Exploit code is publicly available, though no active exploitation has been confirmed (CISA KEV not listed, EPSS score of 0.04% indicates low exploitation probability).
SQL injection in the getOfficeName method of sfturing hosp_order enables remote attackers with low privileges to manipulate the officesName parameter, potentially extracting or modifying database contents. The vulnerability is publicly documented with proof-of-concept exploit code available, though low EPSS score suggests limited real-world exploitation likelihood.
2-3 sentence plain-language. Start with impact: SQL injection vulnerability in favethemes Homey theme for WordPress allows unauthenticated remote attackers to extract sensitive data from the database. Affects versions up to 2.4.5. No known active exploitation (no KEV, EPSS low), but POC not mentioned. The high CVSS is due to network vector and no auth, but scope change indicates impact may be limited to database if no further compromise. Just synthesize:
SQL injection in DirectIQ Email Marketing plugin ≤2.0 for WordPress allows unauthenticated remote attackers to extract sensitive data from the underlying database. The vulnerability carries a CVSS 9.3 critical rating due to its network attack vector, low complexity, and lack of required privileges or user interaction. No public exploit or active exploitation has been confirmed, and EPSS likelihood is very low (0.05%).
SQL injection in the Classiera WordPress classified-ads theme (all versions up to and including 4.0.34) lets remote attackers inject arbitrary SQL through an unauthenticated request path, per the Patchstack advisory that reported it. Because the CVSS vector specifies PR:N and a changed scope, an attacker can reach backend database content without credentials, exposing sensitive data across the WordPress installation. No public exploit has been identified and EPSS is very low (0.05%), indicating no observed weaponization at time of analysis.
SQL injection in the LifterLMS WordPress plugin (versions up to and including 8.0.6) lets remote attackers inject crafted SQL into a vulnerable query, exposing sensitive database contents such as user records, course data, and WordPress secrets. Patchstack assigns a critical 9.3 (CVSS 3.1) with an unauthenticated network vector, though there is no public exploit identified at time of analysis and EPSS exploitation probability is very low (0.06%, 17th percentile). The flaw is a classic CWE-89 improper neutralization of special elements in an SQL command.
SQL injection in ThemeMove Amely WordPress theme (≤3.1.4) allows unauthenticated remote attackers to extract sensitive database data via crafted SQL queries. The vulnerability is network-exploitable with no user interaction, presenting a severe risk to sites using the theme. No public exploit or active exploitation has been confirmed at this time.
SQL injection in GG Bought Together for WooCommerce plugin allows unauthenticated attackers to extract sensitive data from the WordPress database. Affects versions up to 1.0.2. The EPSS exploitation probability is very low (0.05%) and no public exploit or active exploitation has been identified, suggesting limited real-world risk despite the critical CVSS rating.
SQL injection in bicycleSharingServer 1.0 allows authenticated remote attackers to execute arbitrary SQL commands via the selectAdminByNameLike function in AdminController.java, potentially exposing or altering database contents. An exploit is publicly available, though no active exploitation has been confirmed.
SQL injection in bicycleSharingServer's AdminController.java allows remote authenticated low-privilege users to manipulate the Title parameter, potentially leading to limited data exposure or modification. Public exploit code exists (GitHub issue) but no active exploitation reported and EPSS score is low (0.04%), indicating low real-world exploitation likelihood.
SQL injection in huija bicycleSharingServer via the userDao.selectUserByUserNameLike function allows low-privileged remote attackers to execute arbitrary SQL commands. The exploit has been publicly disclosed, and while no active exploitation is confirmed, the vulnerability is present in the rolling-release codebase up to at least commit 7b8a3ba48ad618604abd4797d2e7cf3b5ac7625a. An attacker could extract or modify sensitive data, potentially compromising user accounts or the underlying database.
yubiserver before 0.6 is prone to SQL injection issues, potentially leading to an authentication bypass.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in OpenNMS Horizon and Meridian applications allows SQL Injection. Users should upgrade to Meridian 2024.2.6 or newer, or Horizon 33.16 or newer. Meridian and Horizon installation instructions state that they are intended for installation within an organization's private networks and should not be directly accessible from the Internet.
A SQL injection vulnerability was discovered in the PHPGurukul Dairy Farm Shop Management System 1.3. The vulnerability allows remote attackers to execute arbitrary SQL code via the category and categorycode parameters in a POST request to the manage-categories.php file.
A time-based blind SQL injection vulnerability was identified in the PHPGurukul Dairy Farm Shop Management System 1.3. The vulnerability exists in the manage-companies.php file and allows remote attackers to execute arbitrary SQL code via the companyname parameter in a POST request.
The Owl carousel responsive plugin for WordPress is vulnerable to time-based SQL Injection via the ‘id’ parameter in all versions up to, and including, 1.9 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
CVE-2025-6668 is a critical SQL injection vulnerability in code-projects Inventory Management System 1.0 affecting the /php_action/fetchSelectedBrand.php endpoint via the brandId parameter. An unauthenticated remote attacker can exploit this vulnerability to read, modify, or delete database contents, with disclosed public exploits and active exploitation potential. The CVSS 7.3 score reflects moderate impact across confidentiality, integrity, and availability, though the attack requires no privileges or user interaction.
CVE-2025-6665 is a critical SQL injection vulnerability in code-projects Inventory Management System 1.0, specifically in the /php_action/editBrand.php file's editBrandStatus parameter. An unauthenticated remote attacker can exploit this to execute arbitrary SQL commands, potentially leading to unauthorized data access, modification, or deletion. The vulnerability has been publicly disclosed with a proof-of-concept available, increasing real-world exploitation risk.
CVE-2025-6612 is a critical SQL injection vulnerability in code-projects Inventory Management System 1.0 affecting the /php_action/removeCategories.php endpoint. An unauthenticated remote attacker can manipulate the 'categoriesId' parameter to execute arbitrary SQL queries, potentially leading to unauthorized data access, modification, or deletion. The vulnerability has been publicly disclosed with exploit code available and demonstrates active exploitation potential with a CVSS 7.3 score indicating moderate-to-high severity.
CVE-2025-6611 is a critical SQL injection vulnerability in code-projects Inventory Management System 1.0 affecting the /php_action/createBrand.php endpoint via the brandStatus parameter. The vulnerability allows unauthenticated remote attackers to manipulate SQL queries, potentially resulting in unauthorized data access, modification, or deletion. Public exploit disclosure and active exploitation risk are confirmed.
SQL injection in itsourcecode Employee Management System 1.0 allows remote attackers to manipulate SQL queries via the FirstName parameter in /admin/editempprofile.php. Exploit code is publicly available, though no active exploitation has been confirmed (EPSS 0.06%). The vulnerability requires admin authentication and can lead to unauthorized data access or modification.
SQL injection in Best Salon Management System 1.0 allows remote authenticated attackers to query the application database via the fromdate and todate parameters in /panel/bwdates-reports-details.php. The vulnerability has a low CVSS 4.0 base score (impacts limited to low confidentiality, integrity, availability), with a 0.06% EPSS and no known in-the-wild exploitation despite a publicly disclosed exploit.
SQL injection in SourceCodester Best Salon Management System 1.0 allows authenticated remote attackers to manipulate database queries via the 'editid' parameter in the '/panel/edit-services.php' endpoint. Exploit code is publicly available, though the EPSS score (0.06%) indicates a low probability of exploitation in the wild.
A SQL injection vulnerability in Student Record system Using PHP and MySQL v (CVSS 7.1) that allows a remote attacker. High severity vulnerability requiring prompt remediation.
SQL injection in Best Salon Management System 1.0 allows remote authenticated attackers to execute arbitrary SQL commands via the ID parameter of /panel/stock.php. Exploit code is publicly available, though no active exploitation has been confirmed.
SQL injection in SourceCodester Best Salon Management System 1.0 allows authenticated attackers to manipulate database queries via the Type parameter in /panel/add-services.php. Publicly available exploit code exists, but no active exploitation has been confirmed through CISA KEV. The EPSS score of 0.06% suggests a low probability of widespread exploitation.
We are tasked with producing a comprehensive analysis JSON object. Let's extract data from the input. CVE: CVE-2025-6605 Description: A vulnerability classified as critical was found in SourceCodester Best Salon Management System 1.0. This vulnerability affects unknown code of the file /panel/edit-staff.php. The manipulation of the argument editid leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. CVSS Score: 2.1 (given; but note the vector is 4.0 and score 2.1 is low; possibly the base score of a 4.0 vector: AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N -> that gives a score around 2.0-2.3? Let's check CVSS 4.0 calculator: AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N = base score 2.1 (low). So CVSS 4.0 score 2.1 low severity. The description says "classified as critical" but CVSS base score is low. This might be a discrepancy: the vulnerability is SQL injection but the impact is limited (low integrity, low confidentiality, low availability) likely because of the privileges required (PR:L) and the impact being limited to the application. We'll note that. CWE: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')). That's a broad category, but SQL injection is CWE-89, so CWE-74 is a parent. So we'll mention it. EPSS: 0.06%, 18th percentile (low likelihood of widespread exploitation) POC/Exploit: Publicly available (the references include a GitHub link) KEV: Not mentioned, so not in KEV. So "no public exploit identified at time of analysis" is wrong; there is public exploit. So we'll use "publicly available exploit code exists" (since POC exists). KEV not present so not actively exploited by that metric. Tags: PHP, SQLi CPE: cpe:2.3:a:mayurik:best_salon_management_system:1.0:*:*:*:*:*:*:* — that's the affected product. So product name: "Best Salon Management System" (by Mayurik). But the description says SourceCodester Best Salon Management System. Probably SourceCodester is the source, vendor Mayurik? We'll use "Best Salon Management System" as product name. Now, for each field: product_name: "Best Salon Management System" (1-3 words). So "Best Salon Management System" fits. summary: Need a synthesis. Impact: SQL injection via editid parameter in /panel/edit-staff.php. Remote attack, but requires privileges (PR:L from CVSS, so authenticated? CVSS vector says PR:L, so low privilege, likely a logged-in user). The EPSS is low, but exploit code exists. CVSS base score low (2.1). So summary: "SQL injection in SourceCodester Best Salon Management System 1.0 allows remote authenticated users to inject SQL via the editid parameter in /panel/edit-staff.php. Exploit code is publicly available, but EPSS exploitation probability is low (0.06%). No active exploitation reported (not in KEV)." technical_context: Explain technology: PHP application, SQL injection. The CWE is CWE-74 (Injection). The specific file /panel/edit-staff.php is part of staff editing functionality. The root cause: improper validation/sanitization of the editid parameter, which is directly used in SQL query. The CPE confirms the specific product and version. So mention PHP and SQLi. risk_assessment: CVSS 4.0: AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N — remote network attack, low attack complexity, no user interaction, low privilege required, low impact on confidentiality, integrity, availability, no scope change. Score 2.1 (Low). But the description says "critical" which is inconsistent; we must highlight that CVSS base score is actually low. EPSS 0.06% (low). POC exists but not known to be actively exploited. So risk is low: low privilege required and limited impact, combined with low EPSS, suggest this is a low-priority issue despite the "critical" classification in the description. Also note: the CVSS vector shows PR:L, so authentication needed, limiting attack surface. affected_products: Product: SourceCodester Best Salon Management System version 1.0. CPE: cpe:2.3:a:mayurik:best_salon_management_system:1.0. Advisory references from VulDB. So write: "SourceCodester Best Salon Management System version 1.0 is affected. The vulnerability is in the /panel/edit-staff.php file. Vendor advisory is available at VulDB (https://vuldb.com/?id.313822) and a PoC exploit is hosted on GitHub (https://github.com/Colorado-all/cve/blob/main/Best%20salon%20management%20system/SQL-6.md)." remediation: No patch explicitly mentioned. We need to check input: the description does not mention a fix version, and the references include VulDB entries that might have patch info, but input does not mention a patch. The patch field is not provided, so we must state "No vendor-released patch identified at time of analysis." But we can suggest mitigating controls: restrict access to /panel/edit-staff.php to trusted users, implement input validation/sanitization for the editid parameter, use parameterized queries. Since the vulnerability requires authentication, ensure strong password policies and limit access to admin panel. Note trade-offs. So we'll write: "No official patch is available from the vendor at the time of analysis. As a workaround, restrict access to the administrative panel (/panel/) to trusted IP addresses and require strong authentication. Implement input validation and parameterized queries to prevent SQL injection in the editid parameter. Alternatively, consider disabling the vulnerable functionality if possible, though this may break staff editing features." Specific, actionable. exploit_scenario: "An authenticated low-privileged user sends a crafted editid parameter in a request to /panel/edit-staff.php to inject SQL commands, potentially extracting database contents or altering records." (Since the CVSS impact: low on all three, so not full database compromise, but still data exposure and manipulation). Since exploit is public, an attacker could use the PoC. exploitation_conditions: Conditions: attacker must be authenticated (low privilege), as indicated by CVSS PR:L. No specific non-default configuration required beyond the application being deployed. So we state: "Low-privileged authenticated access to the application's administrative panel is required; no other special conditions are needed beyond default installation." Not just "network access required" generic. We add: "The vulnerability is in /panel/edit-staff.php, so the attacker must have a valid user account with privilege to edit staff (or at least access the panel)." So exact feature: staff editing functionality. That's a concrete condition. attack_chain: Will use 4-step? Steps: Access authenticated session → Send crafted editid parameter → SQL injection executes → Data leakage/manipulation. So: "Authenticate to Best Salon Management System panel → Send crafted HTTP request to /panel/edit-staff.php with malicious editid parameter → SQL injection executes against backend database → Extract or modify database records." With limited impact, so no code execution. confidence_notes: "Exploit code is publicly available, confirmed by GitHub repository. No vendor patch identified; affected product versions confirmed via CPE. EPSS and CVSS derived from VulDB; CVSS 4.0 score is low despite 'critical' classification in description, likely due to the low privileges and limited impact." Also, CWE-74 is broad; the underlying issue is SQL injection. The data from VulDB is the primary source; no NVD analysis yet (just references). So note that. prevalence: "low" – Best Salon Management System is a niche product for salon management, likely small business usage, not ubiquitous. So prevalence: low. prevalence_basis: "niche salon management system, limited enterprise deployment" (less than 12 words). So "low deployment footprint for a specialized salon management application." assessed_cvss_vector: Our independent assessment? Based on description and CVSS 4.0 vector given, it's already a 4.0 vector. We need to provide CVSS 3.1 vector equivalent. We'll convert the 4.0 vector to 3.1 as best we can: AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L. That matches 3.1 base score: (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L) = 6.5 (Medium). Wait, that would be 6.5, not 2.1. The given CVSS 4.0 vector has low impact on VC/VI/VA, which in 4.0 yields low severity because the impact metrics are weighted differently. In 3.1, L/L/L for C/I/A gives 0.22 impact sub-score and 6.5 base. But our vector must be consistent with the actual severity. According to the CVSS 4.0 specification, a vector with AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N yields a score of 2.1 (Low). If we translate that to 3.1, it would be AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L = 6.5, which is Medium. This suggests the 4.0 vector "downgrades" because impact is low? Wait, in 3.1, L/L/L for a low-privilege attack is Medium, not Low. The CVSS 4.0 introduces new severity levels; low score 2.1 might be "Low" in 4.0, but in 3.1 it would be "Medium". So to be independent, we can provide a 3.1 vector that reflects the actual technical risk. But we are asked to provide an independent assessment, grounded in description. I'll assess: The vulnerability is SQL injection, remote, authenticated (low privilege), no user interaction, scope unchanged, impact likely low on confidentiality, integrity, availability? For SQL injection, usually you can extract data, modify data, and possibly cause denial by dropping tables. So impact could be high, but from CVSS it's limited to low maybe because the vulnerable parameter only affects a specific table and the user has low privileges? The description doesn't specify. Given the public exploit likely shows limited injection, but a skilled attacker could escalate. To be cautious, I'd set C:L/I:L/A:L if authentication is needed. So my independent 3.1 vector: AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L (score 6.5). I'll provide that with rationale: "Requires low-privilege authentication, no user interaction, and limited data exposure in default configuration; however, SQL injection can potentially escalate impact." But I'll note that the given CVSS 4.0 vector shows low impact, and I'll reflect that. Actually, the input includes a CVSS vector already, so I could just use that 4.0 vector for assessed_cvss40_vector, but the instruction says "Your OWN independent CVSS 3.1 base-metric vector for THIS vulnerability, grounded in the description and exploitation conditions — NOT a copy of any score in the input." So I'll create my own 3.1, and also a 4.0 that's consistent with my 3.1. Since the input's 4.0 has low impact and low score, my independent assessment might produce a higher impact (e.g., C:H/I:H/A:H) for SQLi, but I need to be grounded in description: The description says it leads to SQL injection, but the CVSS 4.0 given says low impact on all three. Why? Possibly because the attacker is only low privilege and the database user might also have limited permissions, or the injection point is such that only simple injection possible? The description doesn't elaborate. However, typical SQL injection can lead to full database compromise. But the authoritative source is the VulDB entry which assigned low impact. It's risky to overrule that without further data. I'll stick to a moderate approach: I'll assign C:L/I:L/A:L, acknowledging that higher impact might be possible but not confirmed. So rationale: "Authenticated SQL injection with limited impact likely due to restricted database permissions, but could potentially be escalated." So 3.1 vector: CVSS:3.1
SQL injection in Best Salon Management System 1.0 through the Name parameter in /panel/add-staff.php allows authenticated remote attackers to read, modify, or delete database contents. Publicly available exploit code exists, but the low EPSS score (0.06%) and low CVSS impact suggest limited real-world exploitation risk.
CVE-2025-0966 is a SQL injection vulnerability in IBM InfoSphere Information Server 11.7 that allows authenticated remote attackers to execute arbitrary SQL commands against the backend database. An attacker with valid credentials can view, add, modify, or delete sensitive information without administrative privileges. The vulnerability carries a CVSS score of 7.6 (High) and requires low attack complexity, making it a significant risk for organizations using affected versions.
SQL injection in Best Salon Management System 1.0 allows remote attackers with low privileges to manipulate database queries via the viewid parameter in /view-appointment.php. A public proof-of-concept exploit exists but active exploitation is not confirmed. The flaw can lead to unauthorized data access or modification.
SQL injection in SourceCodester Best Salon Management System 1.0 allows remote authenticated attackers to manipulate the editid parameter in /edit-customer-detailed.php, potentially leading to unauthorized data access or modification. A publicly available proof-of-concept exploit exists, but no active exploitation has been confirmed.
SQL injection in SourceCodester Best Salon Management System 1.0 allows low-privileged authenticated attackers to extract or modify database content via the /add-customer.php endpoint. Public exploit code is available, lowering the barrier for exploitation, though no active exploitation has been confirmed (not in CISA KEV) and EPSS indicates a low probability of widespread attacks (0.06%).
CVE-2025-6580 is a critical SQL injection vulnerability in SourceCodester Best Salon Management System 1.0 affecting the Login component's Username parameter. An unauthenticated remote attacker can exploit this vulnerability to execute arbitrary SQL queries, potentially leading to unauthorized data access, modification, or deletion. The vulnerability has been publicly disclosed with proof-of-concept code available, increasing exploitation risk.
CVE-2025-6579 is a critical SQL injection vulnerability in code-projects Car Rental System 1.0 affecting the /message_admin.php file's Message parameter. An unauthenticated remote attacker can exploit this to execute arbitrary SQL commands, potentially leading to unauthorized data access, modification, or deletion. The vulnerability has been publicly disclosed with proof-of-concept code available and may be actively exploited in the wild.
CVE-2025-6578 is a critical SQL injection vulnerability in Simple Online Hotel Reservation System version 1.0 affecting the /admin/delete_account.php file through unsanitized admin_id parameter manipulation. An unauthenticated remote attacker can execute arbitrary SQL queries to read, modify, or delete database contents. The vulnerability has been publicly disclosed with proof-of-concept code available, presenting immediate exploitation risk for deployed instances.
ControlID iDSecure On-premises versions 4.7.48.0 and prior contain SQL injection vulnerabilities that allow unauthenticated remote attackers to execute arbitrary SQL queries, potentially leaking sensitive information or modifying database contents. The CVSS 9.1 score reflects the critical nature (high confidentiality and integrity impact), though availability is not directly affected. Active exploitation status and proof-of-concept availability cannot be confirmed from provided data, but the unauthenticated, network-accessible attack vector makes this a high-priority vulnerability.
SQL injection in PHPGurukul Hospital Management System 4.0 allows remote authenticated attackers to read, modify, or delete database contents via the searchdata parameter in /doctor/search.php. A public proof-of-concept exploit exists, but EPSS indicates a very low exploitation probability (0.06%) and the vulnerability is not listed in CISA KEV.
A remote code execution vulnerability in OS4Ed Open Source Information System Community (CVSS 9.8). Critical severity with potential for significant impact on affected systems.
CVE-2025-6567 is a critical SQL injection vulnerability in Campcodes Online Recruitment Management System version 1.0, specifically in the Recruitment/admin/view_application.php file where the ID parameter is insufficiently sanitized. An unauthenticated remote attacker can exploit this to execute arbitrary SQL queries, potentially leading to unauthorized data access, modification, or deletion of recruitment records. The vulnerability has been publicly disclosed with proof-of-concept code available, and exploitation requires no special privileges or user interaction.
Apache Airflow Providers Snowflake versions before 6.4.0 contain a Special Element Injection vulnerability (CWE-75) in the CopyFromExternalStageToSnowflakeOperator that fails to properly sanitize table and stage parameters, allowing unauthenticated attackers to execute arbitrary SQL injection attacks with complete system compromise (CVSS 9.8). This is a critical remote vulnerability requiring network access only, with no authentication or user interaction needed, making it a high-priority patch regardless of KEV/EPSS status.
CVE-2025-34038 is an unauthenticated SQL injection vulnerability in Weaver E-cology 8.0's getdata.jsp endpoint that allows attackers to execute arbitrary SQL queries by injecting malicious code through the unsanitized 'sql' parameter in the getSelectAllIds() method. The vulnerability affects Weaver E-cology 8.0 and enables attackers to extract sensitive data including administrator password hashes without authentication. Active exploitation has been observed by Shadowserver Foundation as of 2025-02-05, indicating this is a real and present threat in the wild.
SQL injection in Novel-Plus up to 5.1.3 allows authenticated remote attackers to extract sensitive data via the sort/order parameters in the User Management Module. Public exploit code exists, but no active exploitation has been confirmed (not in CISA KEV). EPSS score is low (0.05%), indicating limited exploitation likelihood.
A SQL injection vulnerability (CVSS 9.8) that allows a remote attacker. Risk factors: public PoC available.
CVE-2025-6503 is a critical SQL injection vulnerability in code-projects Inventory Management System 1.0, specifically in the /php_action/fetchSelectedCategories.php file where the 'categoriesId' parameter is inadequately sanitized. An unauthenticated remote attacker can exploit this vulnerability to execute arbitrary SQL queries, potentially leading to unauthorized data access, modification, or deletion. The exploit has been publicly disclosed and proof-of-concept code is available, significantly elevating exploitation risk in production environments.
CVE-2025-6502 is a critical SQL injection vulnerability in code-projects Inventory Management System 1.0, specifically in the /php_action/changePassword.php file where the user_id parameter is inadequately sanitized. An unauthenticated remote attacker can exploit this vulnerability to execute arbitrary SQL commands, potentially leading to unauthorized data access, modification, or deletion. The vulnerability has been publicly disclosed with exploit details available, increasing immediate risk of active exploitation.
CVE-2025-6501 is a critical SQL injection vulnerability in code-projects Inventory Management System 1.0 affecting the /php_action/createCategories.php file, where the 'categoriesStatus' parameter is not properly sanitized. An unauthenticated remote attacker can exploit this to execute arbitrary SQL commands, potentially leading to unauthorized data access, modification, or deletion. Public exploit disclosure and proof-of-concept availability indicate active threat potential with low barrier to exploitation.
CVE-2025-6500 is a critical SQL injection vulnerability in code-projects Inventory Management System 1.0, specifically in the /php_action/editCategories.php file where the 'editCategoriesName' parameter is inadequately sanitized. An unauthenticated attacker can exploit this remotely to read, modify, or delete database contents, affecting confidentiality, integrity, and availability. Public exploit disclosure and confirmed proof-of-concept availability increase real-world risk significantly.
CVE-2025-6489 is a critical SQL injection vulnerability in itsourcecode Agri-Trading Online Shopping System version 1.0, affecting the /transactionsave.php file through the 'del' parameter. An unauthenticated remote attacker can exploit this vulnerability to execute arbitrary SQL commands, potentially compromising confidentiality, integrity, and availability of the application database. Public disclosure of this vulnerability exists, and exploitation is feasible without authentication or user interaction.
SQL injection in code-projects Online Shopping Store 1.0 allows remote authenticated attackers to manipulate database queries via the cat_id, brand_id, keyword, proId, or pid parameters in /action.php. Public exploit code exists, but no active exploitation has been confirmed. EPSS score is low (0.14%), indicating limited exploitation likelihood.
CVE-2025-6483 is a critical SQL injection vulnerability in code-projects Simple Pizza Ordering System version 1.0, specifically in the /edituser.php file's ID parameter. An unauthenticated remote attacker can exploit this weakness to execute arbitrary SQL commands, potentially compromising data confidentiality, integrity, and availability. The vulnerability has been publicly disclosed with exploit code available, increasing the likelihood of active exploitation.
CVE-2025-6482 is a SQL injection vulnerability in Simple Pizza Ordering System 1.0 affecting the /edituser-exec.php endpoint via the userid parameter, allowing unauthenticated remote attackers to execute arbitrary SQL commands and potentially exfiltrate, modify, or delete database contents. The vulnerability has been publicly disclosed with proof-of-concept exploitation available, presenting immediate risk to affected installations. With a CVSS score of 7.3 and network-based attack vector requiring no user interaction, this represents a moderately critical risk requiring urgent patching.
CVE-2025-6481 is a critical SQL injection vulnerability in code-projects Simple Pizza Ordering System 1.0 affecting the /update.php file's ID parameter, allowing unauthenticated remote attackers to manipulate database queries and potentially extract, modify, or delete sensitive data. The vulnerability has been publicly disclosed with proof-of-concept availability, significantly increasing exploitation risk in production environments. With a CVSS score of 7.3 and low attack complexity, this represents an immediate threat to any organization running the affected version without patches.
A SQL injection vulnerability in A vulnerability classified as critical (CVSS 7.3). Risk factors: public PoC available.
CVE-2025-6479 is a critical SQL injection vulnerability in code-projects Simple Pizza Ordering System 1.0 affecting the /salesreport.php file parameter 'dayfrom'. An unauthenticated attacker can remotely execute arbitrary SQL queries with no user interaction required, potentially enabling data exfiltration, modification, or deletion. The vulnerability has been publicly disclosed with exploit proof-of-concept availability, increasing real-world exploitation risk.
CVE-2025-6474 is a critical SQL injection vulnerability in code-projects Inventory Management System version 1.0 affecting the /changeUsername.php file, specifically the user_id parameter. An unauthenticated remote attacker can exploit this vulnerability to execute arbitrary SQL commands, potentially compromising data confidentiality, integrity, and availability. The vulnerability has been publicly disclosed with proof-of-concept availability, making active exploitation likely.
CVE-2025-6472 is a critical SQL injection vulnerability in code-projects Online Bidding System 1.0 affecting the /showprod.php file's ID parameter. An unauthenticated remote attacker can exploit this vulnerability to execute arbitrary SQL queries, potentially leading to unauthorized data access, modification, or denial of service. The vulnerability has been publicly disclosed with exploit code available, creating immediate risk for exposed instances.
CVE-2025-6471 is a critical SQL injection vulnerability in code-projects Online Bidding System version 1.0 affecting the /administrator endpoint, where the 'aduser' parameter is not properly sanitized. An unauthenticated remote attacker can exploit this to execute arbitrary SQL queries, potentially leading to unauthorized data access, modification, or deletion. Public exploit code is available and the vulnerability is actively exploitable with no authentication required.
CVE-2025-6470 is a critical SQL injection vulnerability in code-projects Online Bidding System 1.0, specifically in the /bidlog.php file's ID parameter, allowing unauthenticated remote attackers to execute arbitrary SQL queries. The vulnerability has been publicly disclosed with proof-of-concept code available, presenting immediate exploitation risk. With a CVSS score of 7.3 and network-accessible attack vector requiring no authentication, this poses significant risk to confidentiality, integrity, and availability of affected systems.
A SQL injection vulnerability in A vulnerability (CVSS 7.3). Risk factors: public PoC available.
CVE-2025-6468 is a critical SQL injection vulnerability in code-projects Online Bidding System version 1.0 affecting the /bidnow.php file's ID parameter. An unauthenticated remote attacker can exploit this vulnerability to read, modify, or delete database contents, potentially compromising confidentiality, integrity, and availability of the entire bidding system. The vulnerability has been publicly disclosed with proof-of-concept code available, significantly increasing exploitation risk in active deployments.
CVE-2025-6467 is a critical SQL injection vulnerability in code-projects Online Bidding System version 1.0 affecting the /login.php file's User parameter, allowing unauthenticated remote attackers to execute arbitrary SQL queries and potentially compromise data confidentiality, integrity, and availability. The vulnerability has been publicly disclosed with exploit code available, and while the CVSS score of 7.3 indicates high severity, the attack requires no authentication or user interaction, making it highly exploitable in real-world scenarios.
CVE-2025-6458 is a critical SQL injection vulnerability in code-projects Online Hotel Reservation System version 1.0, affecting the /admin/execedituser.php endpoint. An unauthenticated remote attacker can manipulate the 'userid' parameter to execute arbitrary SQL queries, potentially leading to unauthorized data access, modification, or deletion. The vulnerability has been publicly disclosed with exploit code available, making it actively exploitable in the wild.
CVE-2025-6457 is a critical SQL injection vulnerability in code-projects Online Hotel Reservation System 1.0 affecting the /reservation/demo.php file, where the 'Start' parameter is unsanitized and directly used in database queries. An unauthenticated remote attacker can exploit this vulnerability to read, modify, or delete sensitive database content including guest information, reservations, and payment data. The vulnerability has been publicly disclosed with exploit code available, though specific EPSS probability and KEV/CISA inclusion status cannot be determined from provided data.
CVE-2025-6456 is a critical SQL injection vulnerability in code-projects Online Hotel Reservation System 1.0, specifically in the /reservation/order.php file's 'Start' parameter. An unauthenticated remote attacker can manipulate this parameter to execute arbitrary SQL queries, potentially leading to unauthorized data access, modification, or deletion of the hotel reservation database. Public exploit code is available, and the vulnerability is actively exploitable.
CVE-2025-6455 is a SQL injection vulnerability in code-projects Online Hotel Reservation System version 1.0, specifically in the /messageexec.php file where the 'Name' parameter is insufficiently sanitized. An unauthenticated remote attacker can exploit this to execute arbitrary SQL commands, potentially leading to unauthorized data access, modification, or deletion. The vulnerability has been publicly disclosed with exploit code available, indicating active exploitation risk.
CVE-2025-6451 is a critical SQL injection vulnerability in code-projects Simple Online Hotel Reservation System version 1.0, affecting the /admin/delete_pending.php file where the transaction_id parameter is unsanitized. An unauthenticated remote attacker can exploit this to execute arbitrary SQL queries, potentially leading to data exfiltration, modification, or deletion of the hotel reservation database. Public exploit disclosure and active threat indicators suggest this vulnerability warrants immediate patching.
CVE-2025-6450 is a critical SQL injection vulnerability in code-projects Simple Online Hotel Reservation System version 1.0, affecting the /admin/confirm_reserve.php endpoint where the transaction_id parameter is inadequately sanitized. An unauthenticated remote attacker can exploit this vulnerability to execute arbitrary SQL commands, potentially leading to unauthorized data access, modification, or deletion of the hotel reservation database. Public exploit code is available and the vulnerability meets criteria for active exploitation risk.
CVE-2025-6449 is a critical SQL injection vulnerability in Simple Online Hotel Reservation System v1.0 affecting the /admin/checkout_query.php endpoint. An unauthenticated remote attacker can manipulate the 'transaction_id' parameter to execute arbitrary SQL queries, potentially leading to unauthorized data access, modification, or system disruption. The vulnerability has been publicly disclosed with exploits available, and the CVSS 7.3 score reflects high impact across confidentiality, integrity, and availability despite moderate attack complexity.
CVE-2025-6448 is a critical SQL injection vulnerability in code-projects Simple Online Hotel Reservation System 1.0 affecting the /admin/delete_room.php endpoint. An unauthenticated remote attacker can manipulate the room_id parameter to execute arbitrary SQL queries, potentially resulting in unauthorized data access, modification, or deletion. The vulnerability has been publicly disclosed with working exploits available, making active exploitation likely.
CVE-2025-6447 is a critical SQL injection vulnerability in the Simple Online Hotel Reservation System version 1.0, specifically in the /admin/index.php file's Username parameter. An unauthenticated remote attacker can exploit this vulnerability to execute arbitrary SQL queries, potentially leading to unauthorized data access, modification, or system disruption. The exploit has been publicly disclosed with proof-of-concept code available, significantly increasing the risk of active exploitation.
A critical SQL injection vulnerability exists in code-projects Client Details System version 1.0, specifically in the /clientdetails/admin/index.php file where the Username parameter is improperly validated. An unauthenticated remote attacker can exploit this vulnerability to execute arbitrary SQL commands, potentially leading to unauthorized data access, modification, or deletion. The vulnerability has public exploit code available and demonstrates moderate real-world risk despite the critical classification, with a CVSS score of 7.3 indicating concrete but not maximum severity.
A critical SQL injection vulnerability exists in code-projects Simple Online Hotel Reservation System version 1.0, specifically in the /admin/add_account.php file where the 'name' or 'admin_id' parameters are not properly sanitized. An unauthenticated remote attacker can exploit this vulnerability to execute arbitrary SQL commands, potentially leading to unauthorized data access, modification, or deletion of the hotel reservation database. Public exploit code is available and the vulnerability is actively being disclosed, increasing exploitation risk in the wild.
A critical SQL injection vulnerability exists in code-projects Simple Online Hotel Reservation System version 1.0, specifically in the /admin/add_room.php file where the 'room_type' parameter is insufficiently sanitized. An unauthenticated remote attacker can exploit this vulnerability to execute arbitrary SQL commands, potentially leading to unauthorized data access, modification, or deletion of hotel reservation system data. A proof-of-concept exploit has been publicly disclosed, increasing real-world exploitation risk.
Quick Facts
- Typical Severity
- HIGH
- Category
- web
- Total CVEs
- 16090