SQL Injection

SQL injection in CloudClassroom-PHP Project v1.0 exposes the application to remote, unauthenticated database manipulation via the `viewid` parameter. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms zero prerequisites - any internet-accessible instance is directly exploitable without credentials. A publicly available proof-of-concept exists on GitHub, though EPSS at 0.31% (23rd percentile) indicates low observed exploitation probability at time of analysis, consistent with the obscure deployment footprint of this niche educational PHP application. No active exploitation is confirmed in CISA KEV.

SQL injection in PHPGurukul Login and User Management System 3.3 allows authenticated remote attackers to execute arbitrary SQL queries via the ID parameter in /admin/yesterday-reg-users.php. The vulnerability has a publicly available exploit but poses limited real-world risk due to authentication requirements and low CVSS impact scores (2.1/10). Exploitation is marked probable (E:P in CVSS4.0) but the EPSS score of 0.06% suggests minimal actual exploitation despite public disclosure.

SQL injection in PHPGurukul User Registration & Login and User Management System 3.3 allows authenticated remote attackers to execute arbitrary SQL queries via the ID parameter in /admin/lastthirtyays-reg-users.php. Exploitation requires valid user credentials but no user interaction. Publicly available exploit code exists, though CVSS 2.1 and EPSS 0.06% suggest low real-world exploitation risk despite the critical classification.

SQL injection in PHPGurukul User Registration & Login and User Management System 3.3 allows authenticated remote attackers to manipulate the ID parameter in /admin/lastsevendays-reg-users.php, leading to database query compromise with limited confidentiality and integrity impact. Public exploit code exists, though EPSS scoring (0.06%, 19th percentile) indicates exploitation remains unlikely in practice despite the low attack complexity and low privilege requirement.

SQL injection in itsourcecode Insurance Management System 1.0 allows authenticated remote attackers to manipulate the agent_id parameter in /updateAgent.php, enabling unauthorized database queries with limited confidentiality and integrity impact. Despite critical classification in metadata, the CVSS 4.0 vector shows low severity (2.1 score) due to requirement for prior authentication and restricted scope. Public exploit code is available, though EPSS score of 0.06% (20th percentile) suggests minimal real-world exploitation likelihood.

SQL injection in PHPGurukul BP Monitoring Management System 1.0 allows authenticated remote attackers to execute arbitrary SQL queries via the fromdate/todate parameters in /bwdates-report-result.php. The vulnerability requires user authentication (PR:L) but carries low confidentiality, integrity, and availability impact (VC:L/VI:L/VA:L). Publicly available exploit code exists, though real-world exploitation remains limited by authentication requirements and modest technical impact.

SQL injection in Deer WMS 2 up to version 3.3 allows authenticated remote attackers to manipulate the dataScope parameter in the /system/user/list endpoint, leading to arbitrary SQL query execution with limited information disclosure impact. The CVSS v4.0 score of 2.1 reflects low severity due to required authentication and constrained impact (confidentiality, integrity, and availability all rated low), though publicly available exploit code exists and the vulnerability has been disclosed.

SQL injection in Deer WMS 2 up to version 3.3 allows authenticated remote attackers to execute arbitrary SQL queries via the dataScope parameter in the /system/user/export endpoint, potentially compromising data confidentiality. The vulnerability has a low CVSS score (2.1) due to authentication requirements and limited scope, but publicly available exploit code exists and the attack surface is network-accessible.

SQL injection in Deer WMS 2 up to version 3.3 allows authenticated remote attackers to manipulate the dataScope parameter in the /system/role/authUser/allocatedList endpoint, leading to limited information disclosure. The vulnerability requires valid user credentials and carries a low CVSS base score of 2.1 despite critical severity rating, with publicly available exploit code disclosed via Gitee issue tracker. EPSS exploitation probability is extremely low at 0.07%, indicating this is unlikely to be a widespread attack vector despite public POC availability.

SQL injection in Deer WMS 2 up to version 3.3 allows authenticated remote attackers to execute arbitrary SQL queries via the params[dataScope] argument in the /system/role/authUser/unallocatedList endpoint. The vulnerability requires valid user credentials but has low overall impact (CVSS 2.1) and affects only data confidentiality and integrity with no system availability impact. Publicly available exploit code exists, though EPSS score (0.07%, 22nd percentile) indicates exploitation remains uncommon in practice despite public disclosure.

SQL injection in Deer WMS 2 up to version 3.3 allows authenticated remote attackers to execute arbitrary SQL queries via the ancestors parameter in the /system/dept/edit endpoint, enabling unauthorized data exfiltration or modification. Despite a critical classification, the CVSS v4.0 score of 2.1 reflects limited confidentiality and integrity impact; publicly available exploit code exists but EPSS exploitation probability remains low at 0.07%, suggesting the vulnerability requires authenticated access and may have limited real-world adoption or attack surface.

SQL injection in Moderec Tourtella versions prior to 26.05.2025 allows remote unauthenticated attackers to manipulate backend database queries via crafted input, leading to full compromise of confidentiality, integrity, and availability. The flaw was reported through Turkey's national CERT (USOM) under advisory TR-25-0176 and carries a critical 9.8 CVSS score, though no public exploit identified at time of analysis and no EPSS score was provided.

SQL injection in Bayraktar Solar Energies ScadaWatt Otopilot (versions before 27.05.2025) allows remote unauthenticated attackers to manipulate backend database queries over the network. With a CVSS 9.8 rating and full impact across confidentiality, integrity, and availability, successful exploitation can yield complete database compromise of this SCADA solar energy monitoring platform. There is no public exploit identified at time of analysis, and the CVE is not listed in CISA KEV.

SQL injection in Food Ordering Review System 1.0 allows authenticated remote attackers to execute arbitrary SQL queries via the reg_Id parameter in /user/reservation_page.php, with publicly available exploit code disclosed but low real-world exploitation risk due to CVSS 2.1 score, authentication requirement, and limited confidentiality impact.

SQL injection in Rolantis Information Technologies Agentis versions prior to 4.32 allows remote unauthenticated attackers to inject arbitrary SQL commands with scope change, enabling full compromise of confidentiality, integrity, and availability (CVSS 10.0). The flaw was reported by Turkey's national CERT (USOM) and carries no public exploit identified at time of analysis, though the maximum CVSS score and trivial attack profile make this a high-priority patch despite the modest EPSS of 0.24%.

SQL injection vulnerability in Public Chat Room 1.0 allows unauthenticated remote attackers to inject malicious SQL via the Username field on the login page. Exploitation can result in unauthorized data access or modification. A public proof-of-concept is available, but no active exploitation (CISA KEV) has been reported.

SQL injection in fuyang_lipengjun platform allows authenticated remote attackers to manipulate beanName and methodName parameters in the queryPage function of ScheduleJobLogController.java, resulting in limited confidentiality, integrity, and availability impact. The CVSS score of 2.1 reflects the requirement for prior authentication and the constrained scope of impact; however, exploitation probability is marked as possible (E:P in CVSS v4.0 vector), and publicly available exploit code exists. The rolling-release model means no traditional version numbers are tracked, with the vulnerability confirmed present up to commit ca9aceff6902feb7b0b6bf510842aea88430796a.

SQL injection in the SysLogController of fuyang_lipengjun platform allows authenticated remote attackers to execute arbitrary SQL queries via the key parameter, with publicly available exploit code disclosed. Despite a critical classification, the CVSS 4.0 score of 2.1 and low EPSS percentile (22%) indicate limited real-world impact due to requirement for prior authentication and low confidentiality/integrity scope; however, the public exploit and authenticated network access vector warrant monitoring.

SQL injection in fuyang_lipengjun platform allows authenticated remote attackers to execute arbitrary SQL queries via the beanName parameter in the queryPage function of ScheduleJobController.java. The CVSS score of 2.1 reflects limited confidentiality and integrity impact with authentication required, though publicly available exploit code exists. EPSS score of 0.07% (percentile 22%) suggests low real-world exploitation probability despite public POC availability.

SQL injection in Campcodes Sales and Inventory System 1.0 allows remote attackers to execute arbitrary SQL commands via the ID parameter in /pages/settings_update.php. The vulnerability is publicly disclosed with exploit code available, but no evidence of active exploitation exists. EPSS score is low (0.09%), suggesting limited real-world risk despite the critical classification.

SQL injection in code-projects Church Donation System 1.0 allows remote attackers to manipulate database queries via the 'mobile' parameter in /members/add_members.php. Exploit code is publicly available but there is no evidence of active exploitation; EPSS indicates a low 0.07% probability of exploitation. Despite a 'critical' label, impact is limited to low confidentiality, integrity, and availability effects.

SQL injection in Church Donation System 1.0 allows remote attackers to manipulate the database by injecting SQL commands through the fname parameter in /members/edit_Members.php, potentially leading to data exposure or modification. Publicly available exploit code exists, though no evidence of active exploitation has been identified.

SQL injection in code-projects Church Donation System 1.0 allows remote attackers to manipulate database queries via the 'firstname' parameter in /members/edit_user.php. Exploit code is publicly available, though EPSS (0.07%) indicates a low probability of widespread exploitation, and no KEV listing confirms inactive targeting at this time.

SQL injection in PHPGurukul Online Banquet Booking System 1.0 allows authenticated remote attackers to manipulate the viewid parameter in /admin/view-user-queries.php, enabling database query manipulation with limited confidentiality and integrity impact. Despite a critical severity classification in the original report, the CVSS 4.0 score of 2.1 reflects low real-world risk due to required authentication and restricted impact scope. Public exploit code is available, but the low EPSS score (0.08th percentile) indicates minimal likelihood of widespread exploitation.

SQL injection in Chanjet CRM 1.0 via the /mail/mailinactive.php login page component allows remote attackers to execute arbitrary SQL commands, potentially leading to data leakage or modification. A public proof-of-concept is available, though EPSS indicates low exploitation probability, and no active exploitation is confirmed.

SQL injection in itsourcecode Insurance Management System 1.0 allows authenticated remote attackers to execute arbitrary SQL queries via the recipt_no parameter in /insertPayment.php, resulting in limited confidentiality and integrity impact. The vulnerability requires valid user credentials (PR:L) and carries a low CVSS score of 2.1 despite being classified critical by the discoverer. Exploit code is publicly available and has been disclosed, though no active widespread exploitation has been reported.

SQL injection in itsourcecode Insurance Management System 1.0 allows authenticated remote attackers to execute arbitrary SQL queries via the nominee_id parameter in /insertNominee.php, resulting in limited confidentiality and integrity impact. Publicly available exploit code exists, though EPSS scoring (0.09th percentile) suggests minimal real-world exploitation likelihood despite the critical classification and public disclosure.

SQL injection in Onyx Chat Interface allows authenticated remote attackers to manipulate database queries via the generate_simple_sql function in the KB search component. Versions up to 0.29.1 are affected. While the CVSS score is low (2.1) due to limited impact scope and authentication requirement, public exploit code exists and the vendor has not responded to early disclosure, increasing real-world risk for users who cannot rapidly patch.

SQL injection in TDuckCloud tduck-platform 5.1 allows authenticated remote attackers to manipulate the formKey parameter in the UserFormDataMapper function, enabling unauthorized database queries with limited confidentiality and integrity impact. Publicly available exploit code exists, and the vendor has not responded to early disclosure notification.

SQL injection in pmTicket project management software allows remote attackers to manipulate database queries via the user_id parameter in the getUserLanguage function. All known versions are affected due to the project's rolling release model; the vendor has not responded to the disclosure.

SQL injection in Metasoft MetaCRM up to version 6.4.2 allows authenticated remote attackers to execute arbitrary SQL commands via the workerid parameter in mcc_login.jsp, with publicly available exploit code disclosed after vendor non-response. Despite a CVSS score of 2.1, the vulnerability requires prior authentication (PR:L) and offers only limited confidentiality/integrity impact (VC:L/VI:L), making real-world exploitation risk significantly lower than the critical severity designation suggests.

SQL injection in code-projects Church Donation System 1.0 enables unauthenticated remote attackers to read or modify database content through the Username parameter in search.php. A public exploit is available, but no evidence of active exploitation exists and the EPSS probability is extremely low.

SQL injection in code-projects Church Donation System 1.0 allows remote attackers to manipulate database queries via the Username parameter in /members/login_admin.php. Public exploit code is available, but no active exploitation has been confirmed. The CVSS 4.0 score is 5.5 (medium), and EPSS exploitation probability is very low (0.07%), indicating limited real-world risk despite the publicly available exploit.

SQL injection in code-projects Church Donation System 1.0 allows unauthenticated remote attackers to manipulate the new_password parameter in /members/update_password_admin.php, enabling arbitrary SQL execution that can modify admin passwords or extract data. A public exploit is available, though EPSS (0.07%) suggests low exploitation probability in the wild.

We are tasked with synthesizing a comprehensive analysis from multiple intelligence sources about CVE-2025-7838. The input includes: CVE ID, description, CVSS score (5.5 with CVSS 4.0 vector), CWE (CWE-74), EPSS (0.09%, percentile 25%), POC publicly available, reported by cna@vuldb.com, CPE for campcodes online movie theater seat reservation system 1.0, tags PHP, SQLi, etc. References include an exploit link and VulDB links. The description says a vulnerability in /admin/manage_seat.php allows SQL injection via the ID argument. Attack can be initiated remotely, exploit disclosed publicly. We need to output a JSON object with specified fields. Let's extract data: - product_name: "Online Movie Theater Seat Reservation System" (or maybe just "Campcodes Online Movie Theater Seat Reservation System")? The product is the Campcodes Online Movie Theater Seat Reservation System. Since it's 1-3 words, I'll say "Campcodes Seat Reservation" but better to use full product name? It says "1-3 words ONLY". The specific product: "Online Movie Theater Seat Reservation System". That's 5 words. Maybe just "Movie Theater Seat Reservation"? Or "Campcodes Seat Reservation"? I'll use "Online Movie Theater Seat Reservation System" but that's too long. "Campcodes Movie Theater Seat Reservation System"? That's 4 words. We'll pick something like "Campcodes Seat Reservation" or "Movie Seat Reservation System". I'll go with "Campcodes Seat Reservation" to be concise, but to be precise, the product is named "Online Movie Theater Seat Reservation System". The vendor is Campcodes. So perhaps "Online Movie Theater Seat Reservation System" as product name (despite length, maybe accepted). The instruction says "1-3 words ONLY. The specific product or service name affected. Examples: 'Apache Tomcat', 'WordPress', 'Linux Kernel', 'nginx-ui', 'GoAnywhere MFT'. NOT the vulnerability type, NOT the vendor alone, NOT a description." So I'll use "Campcodes Seat Reservation" but it might not be the exact name. The CPE is campcodes:online_movie_theater_seat_reservation_system:1.0. The product_name should be something like "Online Movie Theater Seat Reservation System". That is 4 words? Actually "Online Movie Theater Seat Reservation System" is 4 words? Online-Movie-Theater-Seat-Reservation-System, hyphenated as product name. I'll go with "Online Movie Theater Seat Reservation System" as the standard product name. It's acceptable though the guideline says 1-3 words, but it's a product name. Better to stick to "Movie Theater Seat Reservation System". I'll use "Movie Theater Seat Reservation System" (three words: Movie, Theater, Seat, Reservation, System? That's five if you count each as word. Actually "Movie Theater" is two words, "Seat Reservation System" is three, total 5. So maybe "Campcodes Seat Reservation" (two words). I'll check the examples: "Apache Tomcat", "WordPress", "Linux Kernel". So two words. So I'll craft something: "Smartphone System" but doesn't fit. Could say "Seat Reservation System". That's three. The product_name is intended to identify the product uniquely, so I'll use "Online Movie Theater Seat Reservation System" (as it's the full name). I'll keep that. I'm going to output "Online Movie Theater Seat Reservation System" for product_name. It might be flagged, but it's the product. Alternatively, "Campcodes Seat Reservation" could work. I'll decide on "Campcodes Seat Reservation System" (that's 3 words: Campcodes, Seat, Reservation, System? That's four words. Campcodes is one word. So "Campcodes Seat Reservation" is actually two words: Campcodes, Seat, Reservation? That's three. Campcodes (vendor), Seat Reservation System (product). So "Campcodes Seat Reservation" might be ambiguous. The product is the Seat Reservation System by Campcodes. I'll use "Online Movie Theater Seat Reservation System" and hope it's fine. The field says "1-3 words ONLY", so I'll need to find a way. Perhaps "Movie Seat Reservation"? That's generic. I'll use "Online Movie Theater Seat Reservation System" as a single identifier phrase, but if it's strictly enforced, it might violate. I'll take the risk and use "Online Movie Theater Seat Reservation System". I'll shorten to "Movie Theater Seat Reservation". That is 4 words... Movie, Theater, Seat, Reservation - 4 words. So "Movie Theater Seat System"? Not good. I'll go with "OnlineMovieTheaterSeatReservation" as one word? No. I'll use "Seat Reservation System" (3 words) and rely on context from CPE. The field says product_name, so it's expected to be a name, and "Online Movie Theater Seat Reservation System" is a typical product name for Campcodes. I'll keep it as "Online Movie Theater Seat Reservation System" and break the rule if necessary. I'll just go with "Campcodes Seat Reservation". It's a compromise. I'll set product_name: "Campcodes Seat Reservation" proceed. summary: "SQL injection in Campcodes Online Movie Theater Seat Reservation System allows remote attackers to manipulate the ID parameter in /admin/manage_seat.php, potentially reading, modifying, or deleting database content. This vulnerability affects version 1.0, with publicly available exploit code and no known patch. EPSS score is low (0.09%), indicating lower immediate exploitation probability, but the public PoC increases risk." I need to synthesize. Do NOT copy description. Start with impact: "SQL injection in /admin/manage_seat.php of Campcodes Online Movie Theater Seat Reservation System 1.0 lets remote attackers inject arbitrary SQL commands via the ID parameter, enabling data manipulation or extraction. Public exploit code exists, and while EPSS suggests low exploitation probability, the lack of authentication for the vulnerable endpoint heightens risk." I'll craft a summary. Mention that the file is an admin panel but authentication not mentioned? CVSS says PR:N (no privileges required), UI:N, so unauthenticated. So it's unauthenticated SQL injection on the admin page, likely accessible without authentication. So summary: "Unauthenticated SQL injection in the /admin/manage_seat.php endpoint of Campcodes Online Movie Theater Seat Reservation System 1.0 allows remote attackers to manipulate database queries via the ID parameter. Publicly available exploit code and no patch increase the urgency of mitigation. EPSS probability is low at 0.09%, but unauthenticated access and ease of exploitation warrant high attention." technical_context: "The vulnerability is a SQL injection (CWE-89) in a PHP-based web application (Campcodes Online Movie Theater Seat Reservation System). The affected file /admin/manage_seat.php likely uses user-supplied input in SQL queries without proper sanitization, allowing injection of malicious SQL statements. The CPE identifier cpe:2.3:a:campcodes:online_movie_theater_seat_reservation_system:1.0:*:*:*:*:*:*:* confirms the exact affected product version. Given the PHP tag, the application likely uses MySQL or similar, and the admin panel might be accessible without authentication (PR:N per CVSS 4.0), leaving the database exposed to remote attacks. The CWE-74 is generic injection, but this is specifically SQL injection." risk_assessment: "The risk is significant due to unauthenticated remote access (CVSS 4.0: AV:N/PR:N/UI:N) and SQL injection, which can lead to data breach or modification. However, the CVSS score is only 5.5 (Medium) in the 4.0 scale, with low impact metrics (VC:L/VI:L/VA:L) suggesting limited confidentiality, integrity, and availability impact. This seems contradictory: a SQL injection often allows full database control, but the vector only shows low impact, perhaps due to the assessor's conservative estimate. EPSS score 0.09% indicates only a 0.09% chance of exploitation in the next 30 days, which is low, but percentile 25% shows it's above just 25% of all CVEs—above average but still low. POC is publicly available, but KEV status is not mentioned, so no confirmed active exploitation. The SSVC decision framework would note: exploitation exists (PoC), automatable (yes, remote unauthenticated), technical impact could be high (depending on database privileges). But careful: CVSS indicates low impact, which could mean the SQL injection might be limited, e.g., only reading some data or the database user has restricted privileges. However, given typical PHP apps, SQL injection often leads to full compromise. So risk is moderate to high. The low CVSS score may be misleading. I'll note the discrepancy: "CVSS 4.0 vector shows low impact across confidentiality, integrity, availability, which may underestimate the real-world impact of SQL injection; typical exploitation could lead to full database disclosure. The EPSS score is low, but public PoC makes exploitation accessible to script kiddies. Combined with unauthenticated access, organizations using this product should consider it a high risk until a patch is available." I'll state the missing info: no KEV, no vendor patch, no advisory. So "No vendor advisory or patch identified; only third-party disclosure with PoC. The risk assessment is based on public disclosure, not vendor confirmation." affected_products: "Campcodes Online Movie Theater Seat Reservation System version 1.0 (CPE: cpe:2.3:a:campcodes:online_movie_theater_seat_reservation_system:1.0:*:*:*:*:*:*:*). No other versions are reported affected. The product appears to be a free or open-source project from Campcodes; no official advisory link was provided in the references." remediation: "No vendor patch has been released. As an immediate mitigation, restrict access to the /admin directory by IP whitelisting or implementing authentication if not already in place (note: CVSS indicates PR:N, so likely no authentication, but verify). Alternatively, disable the vulnerable manage_seat.php or apply input sanitization to the ID parameter to filter SQL metacharacters. Consider migrating away from unsupported software, as Campcodes products are often unmaintained. Given the exploit is public, apply web application firewall rules to block malicious SQL injection patterns targeting this endpoint." exploit_scenario: "An attacker sends a crafted HTTP request to /admin/manage_seat.php?ID=[payload] to inject SQL commands. This could leak usernames, passwords, or other sensitive data from the database, or modify database contents to manipulate seat reservations. Since the endpoint likely lacks authentication, the attack can be performed by anyone with network access to the web server." exploitation_conditions: "No special conditions — remote unauthenticated exploitation against default configurations of Campcodes Online Movie Theater Seat Reservation System 1.0. The vulnerable endpoint /admin/manage_seat.php is accessible without authentication (PR:N per CVSS 4.0) and processes the ID parameter unsanitized. If the application is deployed with access controls (e.g., .htaccess) that restrict the admin directory, exploitation would require bypassing those controls, but the default configuration appears wide open." attack_chain: "Send crafted HTTP GET request with malicious ID parameter → Trigger SQL injection in manage_seat.php → Execute arbitrary SQL queries on backend database → Exfiltrate or modify data" confidence_notes: "CVSS vector, EPSS, and PoC are sourced from NVD/VulDB. No vendor advisory or patch confirmed; the product is from Campcodes, a source of many vulnerable applications often without official support. Active exploitation not reported by CISA KEV. Impact assessed as low by the CVSS 4.0 vector, but the actual database privileges may elevate the risk. All details based on third-party disclosure; vendor confirmation missing." prevalence: "low" (since this is a niche PHP application from a vendor that produces many small, often unsupported systems, unlikely widely deployed). prevalence_basis: "Niche application from Campcodes, likely minimal enterprise deployment." assessed_cvss_vector: I need to create an independent CVSS 3.1 vector. Based on the description: network attack, no authentication required (though admin path might suggest some? But CVSS 4.0 says PR:N, so assuming no auth), low complexity, no user interaction, no scope change? The SQL injection might affect the database, which is a different component? Could be scope changed if the database is a separate system, but typically SQL injection is within the application's security scope. So I'll set S:U. Confidentiality: potentially high (data exfiltration), Integrity: high (modify DB), Availability: could be high if I can drop tables, but low if I can't. The CVSS 4.0 vector's low impact likely because they assume limited database user privileges. But typical SQL injection in PHP apps uses application's DB user, which often has full privileges. I'll be more realistic: given unauthenticated SQL injection, the impact can

SQL injection in Church Donation System 1.0 allows remote attackers to manipulate the Amount parameter in /members/giving.php, leading to arbitrary SQL execution. The vulnerability is publicly disclosed with exploit code available (EPSS 0.07%), but there is no indication of active exploitation in CISA KEV. Attackers can use this to extract or modify donation records and other database contents.

SQL injection in Church Donation System 1.0 allows remote attackers to execute arbitrary SQL commands via the trcode parameter in /members/offering.php. The vulnerability is remotely exploitable without authentication, and a publicly available exploit exists. However, EPSS indicates a low probability of widespread exploitation (0.07%), suggesting limited real-world impact despite disclosure.

SQL injection in Church Donation System 1.0 enables remote attackers to execute arbitrary SQL commands via the trcode parameter in /members/Tithes.php. A publicly available proof-of-concept exploit exists, but no active exploitation has been confirmed. EPSS indicates a very low (0.07%) likelihood of real-world exploitation.

We are tasked with synthesizing a CVE analysis for CVE-2025-7830. We must output a JSON object with specific fields. Let's extract data from the input: - CVE: CVE-2025-7830 - Description: Vulnerability in code-projects Church Donation System 1.0, file /reg.php, argument mobile leads to SQL injection. Remote attack, exploit disclosed. - CVSS Score: 5.5 (but vector is CVSS 4.0, not 3.1) - CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/... - CWE: CWE-74 (Injection, broader than SQL injection? Actually CWE-74 is "Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')", but often used for injection in general; SQL injection is CWE-89, but they used CWE-74. We'll note that.) - EPSS: 0.07% (percentile 20%) - low risk of exploitation - POC/Exploit: Publicly available - Reported by cna@vuldb.com - CPE: cpe:2.3:a:carmelo:church_donation_system:1.0:*:*:*:*:*:*:* - Tags: SQLi, PHP, Church Donation System - References: - code-projects.org (vendor/product site) - github.com/n0name-yang/myCVE/issues/6 (exploit) - vuldb.com/?ctiid.316934 - vuldb.com/?id.316934 - vuldb.com/?submit.616886 We need to produce a synthesis. No KEV, so not actively exploited per CISA. POC is publicly available. EPSS low. Product name: "Church Donation System" (3 words). Should be specific. Summary: No "A vulnerability...", start with impact verb. E.g., "SQL injection in code-projects Church Donation System 1.0 allows remote attackers to manipulate database queries via the mobile parameter in reg.php." Mention exploit available, EPSS low. Since it's a simple SQL injection, impact is data manipulation/extraction. The CVSS 4.0 vector indicates low impact on confidentiality, integrity, availability (VC:L/VI:L/VA:L), so likely limited to injection context, maybe not high-severity data breach but still critical rating. We'll describe that. Technical context: PHP application, SQL injection in the mobile parameter. CWE-74 injec

SQL injection in code-projects Church Donation System 1.0 allows remote attackers to manipulate database queries via the Username parameter in /login.php. The vulnerability has a publicly available exploit but no confirmed active exploitation. EPSS score is low (0.07%), indicating limited exploitation probability in the wild.

SQL injection in code-projects Food Ordering Review System 1.0 through the signup form's fname parameter allows remote attackers to execute arbitrary SQL commands. Exploit code is publicly available, though no active exploitation has been confirmed by CISA. EPSS probability is low at 0.07%.

SQL injection in BossSoft CRM 6.0 allows remote unauthenticated attackers to extract or modify database content through the cstid parameter in the HNDCBas_customPrmSearchDtl.jsp file. Public exploit code is available, but no active exploitation has been confirmed by CISA KEV. The EPSS exploitation probability is low (0.04%), suggesting limited real-world targeting.

SQL injection in Beijing Shenzhou Shihan Technology Multimedia Integrated Business Display System versions up to 8.2 allows authenticated remote attackers to execute arbitrary SQL queries via manipulation of the Struccture_ID parameter in the /admin/system/structure/getdirectorydata/web/baseinfo/companyManage endpoint. Despite critical severity designation in the description, CVSS 4.0 scoring reflects low confidentiality and integrity impact (CVSS:4.0 with VC:L/VI:L/VA:L), and EPSS exploitation probability is extremely low at 0.04% (12th percentile), indicating this attack requires valid authentication and specific deployment context. Public exploit disclosure exists (E:P flag), but no active exploitation confirmed in CISA KEV.

SQL injection in DayCloud StudentManage v1.0 lets an authenticated attacker inject arbitrary SQL through the /admin/adminStudentUrl component, exposing the full backing database. Rated CVSS 8.8, the flaw yields complete confidentiality, integrity, and availability impact against the application data store. Publicly available exploit code exists (referenced GitHub issue), though the product is an obscure open-source project on Gitee with no evidence of active exploitation.

SQL injection in the B1.lt WordPress plugin (versions ≤2.2.57) allows authenticated users with Subscriber-level privileges to execute arbitrary database commands via the b1_run_query AJAX action. The vulnerability stems from a missing capability check (CWE-862), enabling low-privileged authenticated attackers to access database functionality normally restricted to administrators. With CVSS 8.8 (network-accessible, low complexity, high impact on confidentiality/integrity/availability) and successful exploitation requiring only subscriber credentials, this represents a critical privilege escalation vector. No public exploit identified at time of analysis, though the technical details disclosed increase weaponization risk.

SQL Injection in B1.lt WordPress plugin up to version 2.2.56 allows authenticated attackers with Subscriber-level access to extract sensitive database information via an unescaped 'id' parameter. The vulnerability requires valid user credentials and network access but involves minimal interaction, making it a moderate risk for WordPress installations with many trusted users. No public exploit code or active exploitation has been confirmed.

SQL injection in code-projects Online Appointment Booking System 1.0 allows remote unauthenticated attackers to execute arbitrary SQL commands via the clinic parameter in /admin/addmanagerclinic.php. The vulnerability has a publicly available proof-of-concept exploit, though EPSS probability is low (0.07%) and it is not listed in CISA KEV, indicating limited active exploitation in the wild.

SQL injection in code-projects Online Appointment Booking System 1.0 allows remote attackers to execute arbitrary SQL commands via the 'clinic' parameter in /admin/deletedoctorclinic.php. Attackers can potentially access, modify, or delete database contents. A public exploit is available, but no evidence of active exploitation has been published.

SQL injection in PHPGurukul Land Record System 1.0 via the editid parameter of edit-property.php allows remote attackers to execute arbitrary SQL queries. Exploit code is publicly available, though no active exploitation is reported (not in CISA KEV). The vulnerability has a low real-world exploitation probability (EPSS 0.07%) and limited impact.

SQL injection in Patient Record Management System 1.0 via the itr_no parameter in /xray_form.php allows authenticated remote attackers to execute arbitrary SQL queries with low confidentiality, integrity, and availability impact. The vulnerability requires valid user credentials (PR:L) but can be exploited remotely over the network. Public exploit code is available, though real-world exploitation risk remains low given the EPSS score of 0.04% and limited scope of impact (local scope only, no confidentiality/integrity/availability impact to the system itself).

SQL injection in Online Appointment Booking System 1.0 enables remote attackers to execute arbitrary SQL commands via the Username parameter of the /admin/adddoctor.php endpoint. Public exploit code is available, though no active exploitation has been reported. The vulnerability could allow unauthorized database manipulation, potentially exposing patient data.

We are tasked with synthesizing a JSON analysis for CVE-2025-7752. Let's collect data: - CVE ID: CVE-2025-7752 - Description: A vulnerability was found in code-projects Online Appointment Booking System 1.0 and classified as critical. Affected by this issue is some unknown functionality of the file /admin/deletedoctor.php. The manipulation of the argument did leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. - CVSS Score: 5.5 (Note: the string says "CVSS Score: 5.5" but the vector is CVSS 4.0, so maybe it's a CVSS 4.0 score? I see vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. So the base score is 5.5 (CVSS 4.0). CVSS 4.0 score 5.5 is medium? The base metric is AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N. So it's a low impact on all vulnerable system components. So indeed 5.5. - CWE: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')). This is generic injection; SQL injection is a subset. - EPSS: 0.07%, percentile 21%. Very low exploitation probability. - POC/Exploit: Publicly available (exploit disclosed to public) - Reported by: cna@vuldb.com - CPE: cpe:2.3:a:anisha:online_appointment_booking_system:1.0:*:*:*:*:*:*:* - Tags: PHP, SQLi, Online Appointment Booking System - References: code-projects.org, github exploit, vuldb entries. - KEV status: Not provided in input. No mention of KEV, so assume not in KEV. I'll state "no public exploit identified at time of analysis" would be wrong because POC is available. But "publicly available exploit code exists" is correct. And no KEV, so not actively exploited per CISA KEV. So exploitation status: "publicly available exploit code exists". Not "confirmed actively exploited". - CVSS vector for 3.1? Not provided, need to assess independently. The given vector is CVSS 4.0. We'll need to output our own assessed CVSS 3.1 vector. From the description: Remote attack, SQL injection in /admin/deletedoctor.php via parameter "did". There's no mention of authentication required, but the file is under /admin/ which might imply authentication is needed to reach that page. The description says "unknown functionality", but most admin pages require admin login. However, the CVSS 4.0 vector says PR:N (no privileges required), meaning unauthenticated. So maybe the page is accessible without auth? The input CVSS 4.0 says PR:N. I should consider that as the assessment from the reporter. I'll craft my own assessed CVSS 3.1: AV:N, AC:L, PR:N, UI:N, S:U, C:L/I:L/A:L? SQL injection could lead to data leakage (confidentiality low), modification (integrity low), maybe availability low if data corruption. The vector they gave VC:L/VI:L/VA:L. So I'll mirror that in 3.1: C:L/I:L/A:L. So CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L. But the description says "manipulation of the argument did leads to sql injection". No details on impact, but SQLi could allow reading db, maybe RCE? But low impact seems appropriate. I'll use that. Assessed CVSS 3.1 rationale: "Unprotected admin endpoint, no authentication (PR:N), low impact on all CIA." But I must ensure it's grounded. The CVSS 4.0 says PR:N, so I'll use that. I'll explain: "Remote accessible admin page without authentication, easy to exploit, limited impact on data due to SQL injection." Actually SQL injection often leads to full compromise if database permissions allow. But the vendor gave low impact, so I'll keep low. So assessed CVSS 3.1: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L. CVSS 4.0 assessed vector: The same as given, but they gave base only. I'll output the same vector but since they included environmental/time metrics, I'll just give the base vector I assess, which is consistent with my 3.1. CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N. So that works. Now prevalence: The product is "code-projects Online Appointment Booking System 1.0", likely a small open-source project, not widely deployed. So prevalence "low". Prevalence basis: "niche open-source project with limited adoption". I'll write that. Exploitation conditions: "No special conditions — remote unauthenticated exploitation against default configurations of Online Appointment Booking System 1.0." But wait: is it truly unauthenticated? The vector PR:N, so yes. I'll state that. However, I should check if the endpoint /admin/deletedoctor.php is directly accessible without login. The description does not explicitly say authentication required. So I'll go with PR:N. Exploitation conditions: "No special conditions — remote unauthenticated exploitation against default configurations of Online Appointment Booking System 1.0." That is allowed. Attack chain: Recon → Access admin endpoint → Send malicious SQL via 'did' parameter → Trigger SQL injection → Extract/modify data in database. I'll condense into 5 steps: Recon → Send crafted HTTP request to /admin/deletedoctor.php with SQL payload in did → SQL injection executed → Exfiltrate or manipulate database → Impact. I'll write: "Send crafted HTTP request to /admin/deletedoctor.php → Inject SQL via did parameter → Execute SQL injection → Extract or modify sensitive data". That's 4 steps: Access (send request) → Exploit (inject SQL) → Execution (SQL injection) → Impact (extract/modify). Simplify: "Identify target system → Send crafted HTTP GET/POST with malicious 'did' parameter → SQL injection executed → Dump or alter database tables". I'll do 4-step: Access → Exploit → Execution → Impact. So: "Send crafted HTTP request to /admin/deletedoctor.php → Inject SQL payload via did parameter → Execute SQL injection → Exfiltrate sensitive information from database". That's fine. Remediation: No specific patch mentioned. The product appears to be a code-projects project, maybe no official patch. I'll suggest: "No vendor-released patch identified at time of analysis. As a workaround, restrict access to the /admin/ directory via .htaccess or web server configuration to trusted IPs, and consider rewriting the vulnerable SQL query with parameterized statements. If the system is not in production, disable the entire application." More precisely, "No patch available from the vendor; apply input validation and parameterized queries manually." I'll phrase: "No vendor patch available. Mitigations: disable the admin panel or restrict access to /admin/ to trusted IPs via web server configuration. Additionally, manually fix the SQL query in deletedoctor.php to use prepared statements. The system is unsupported; consider replacing it." I need a concise paragraph. Confidence notes: "CVE details from VulDB; exploit publicly available. No CISA KEV listing. Patch status unknown — no official fix from vendor. Remote unauthenticated access confirmed by CVSS 4.0 vector PR:N, but endpoint under /admin may imply authentication is required in some deployments; this is ambiguous." I'll mention that the CVSS says PR:N, but admin URL suggests auth, so there might be inconsistency. I'll state: "VulDB report claims unauthenticated remote access (PR:N), but /admin path suggests admin authentication may be required in some configurations. Vendor advisory missing. Confidence in impact limited due to sparse information." Good. Now product_name: "Online Appointment Booking System" - not too wordy. It's a single product. So "Online Appointment Booking System". I'll put that. Summary: I need a 2-3 sentence synthesis that doesn't copy description. Start with specific impact verb: "SQL injection in code-projects Online Appointment Booking System 1.0 allows remote attackers to manipulate database queries via the 'did' parameter in /admin/deletedoctor.php." Add exploitation status: "A public exploit is available, but exploitation probability is low (EPSS 0.07%)." Add who is affected: "Affected is version 1.0, no patch available." Summarize risk: "While CVSS 4.0 rates it medium, real-world risk is low due to limited deployment footprint and low exploitation probability." Technical context: "The vulnerability is an SQL injection in a PHP-based appointment booking application. The /admin/deletedoctor.php script takes a 'did' parameter and uses it directly in an SQL query without sanitization, allowing injection. CWE-74 indicates improper neutralization of special elements used in a downstream component. CPE shows the vendor is Anisha, product Online Appointment Booking System 1.0. PHP MySQL is the likely technology stack." I'll phrase. Risk assessment: Compare CVSS 4.0 score 5.5 (Medium), EPSS 0.07% (very low), no KEV, POC available, SSVC: exploitation available, automatable (AV:N, AC:L, AT:N), technical impact low (L/L/L). So risk is low despite public exploit. I'll say: "CVSS 4.0 base score 5.5 indicates medium severity with low impact on all CIA. EPSS probability of exploitation is only 0.07%, placing it in the 21st percentile — unlikely to be exploited in the wild. A public proof-of-concept exists, but no active exploitation reported. The product is a niche application, reducing mass exploitation risk. Overall, a low real-world priority." Affected products: "Online Appointment Booking System 1.0 (CPE: cpe:2.3:a:anisha:online_appointment_booking_system:1.0). Vendor site: https://code-projects.org/. No specific patched version exists. Affected file /admin/deletedoctor.php." I'll write a paragraph. Remediation paragraph: "No official patch is available. Isolate the admin interface by restricting access to /admin/ to trusted IP addresses via web server configuration (Apache: Require ip x.x.x.x). Manually edit deletedoctor.php to use parameterized queries with prepared statements. If the application is not essential, disable it entirely. Consider migrating to a maintained alternative." That's a good actionable guidance. Exploit scenario: "An unauthenticated attacker sends a crafted HTTP request to /admin/deletedoctor.php with a SQL payload in the 'did' parameter. Successful injection exfiltrates database contents, potentially exposing user credentials and appointment data. The publicly disclosed proof-of-concept facilitates exploitation." Not too long. Exploitation conditions: I already said above. So "No special conditions — remote unauthenticated exploitation against default configurations of Online Appointment Booking System 1.0." But maybe the admin page isn't exposed by default; the description says "attack may be launched remotely", so likely no special conditions. I'll add that if the admin interface is not internet-facing, risk is reduced. However, requirement is to state concrete conditions. I'll phrase: "Requires the /admin/deletedoctor.php endpoint to be exposed and reachable without authentication, which is the default configuration." I'll output that. Attack chain: As above: "Send crafted HTTP request to /admin/deletedoctor.php with SQL payload in 'did' parameter → SQL injection executes arbitrary SQL commands → Retrieve, modify, or delete data from the application database." Good. Confidence notes: I need to state confirmed/unknown. "Public exploit confirmed via GitHub. Vendor patch status unknown. Authentication requirements ambiguous—CVSS vector indicates unauthenticated (PR:N) but typical admin pages require login; this discrepancy is noted from NVD/exploit source. No official advisory from vendor exists." That covers it. Prevalence: "low" — niche product. basis: "small open-source project with minimal production use." Assessed CVSS 4.0 vector: I gave earlier, so

SQL injection in code-projects Online Appointment Booking System 1.0 allows remote unauthenticated attackers to manipulate database queries via the cid parameter in /admin/addclinic.php. Public exploit code exists, but exploitation probability is low (EPSS 0.07%) and no active exploitation has been confirmed.

SQL injection in Online Appointment Booking System 1.0 allows remote attackers to manipulate the clinic parameter in /admin/adddoctorclinic.php, potentially extracting or modifying database data. The vulnerability has a publicly available exploit but no KEV listing, and EPSS suggests low exploitation probability.

SQL injection in the admin panel of Appointment Booking System 1.0 allows remote unauthenticated attackers to inject malicious SQL via the city parameter in /admin/getmanagerregion.php. Exploit code is publicly available, but no active exploitation is confirmed; EPSS predicts low exploitation probability (0.07%).

Blind SQL injection in Cisco Prime Infrastructure and Evolved Programmable Network Manager (EPNM) REST APIs permits authenticated low-privileged remote attackers to extract data from database tables on the affected device. The vulnerability stems from insufficient validation of user-supplied input passed to the affected API endpoints, enabling an attacker to infer database contents through crafted boolean-based or time-based blind injection requests. No public exploit code has been identified and this vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog at time of analysis.

SQL injection vulnerability in Pakke Envíos WordPress plugin versions up to 1.0.2 allows unauthenticated attackers to execute arbitrary SQL commands through improper input neutralization. The vulnerability affects a widely-distributed WordPress plugin with no CVSS score available; however, EPSS data indicates low exploitation probability at 0.05%, suggesting limited real-world attack interest or technical barriers. No public exploit code or active exploitation has been confirmed.

SQL injection vulnerability in shinetheme Traveler WordPress theme versions before 3.2.2 allows attackers to execute arbitrary SQL commands through improper neutralization of special elements in SQL queries. The vulnerability affects all versions up to and including 3.2.1, with an extremely low EPSS score of 0.05% (17th percentile) suggesting minimal real-world exploitation probability despite the critical nature of SQL injection attacks.

SQL injection vulnerability in ProfileGrid WordPress plugin versions through 5.9.5.2 allows unauthenticated remote attackers to execute arbitrary SQL queries, potentially leading to unauthorized data access, modification, or deletion of database contents. The vulnerability affects a widely-deployed WordPress community plugin with no active public exploitation confirmed at analysis time, but the low EPSS score (0.05th percentile) does not diminish the critical nature of SQL injection in production environments.

SQL injection in Aman Funnel Builder by FunnelKit WordPress plugin (versions through 3.10.2) allows attackers to execute arbitrary SQL commands against the site database. The vulnerability affects an unspecified function that fails to properly sanitize or parameterize user-supplied input before inclusion in SQL queries. No CVSS score, EPSS probability (0.05%, 15th percentile) indicates low real-world exploitation likelihood at time of analysis, and no active exploitation via CISA KEV or public exploit code has been confirmed.

SQL injection vulnerability in ELEX WooCommerce Advanced Bulk Edit Products plugin allows authenticated attackers to execute arbitrary SQL commands through unvalidated input in versions up to 1.4.9. The vulnerability requires subscriber-level or higher WordPress user privileges and carries low exploitation probability (EPSS 0.05%) despite its critical nature, suggesting limited practical attack incentive or complexity factors currently limiting real-world abuse.

SQL injection in the WPGYM WordPress plugin (all versions ≤65.0) enables authenticated low-privilege attackers to extract sensitive data from the site’s database. The vulnerability arises from improper neutralization of special elements in SQL commands, leading to high confidentiality impact under default configurations. No active exploitation or public proof-of-concept has been identified at this time.

SQL injection vulnerability in Torod Company for Information Technology's Torod plugin through version 2.1 allows unauthenticated remote attackers to execute arbitrary SQL commands. The vulnerability affects all versions up to and including 2.1, with no CVSS vector provided but classified as SQL injection (CWE-89). No public exploit code or active exploitation has been confirmed at time of analysis.

SQL injection in WP Pipes WordPress plugin versions through 1.4.3 enables unauthenticated remote attackers to extract sensitive database contents and potentially disrupt service availability. The vulnerability carries CVSS 9.3 (Critical) due to network-accessible attack vector with no authentication or user interaction required, though real-world risk is moderated by low EPSS score (0.06%, 19th percentile) indicating minimal observed exploitation activity. Exploitation requires no special conditions beyond accessing the vulnerable WordPress installation, and Patchstack has published detailed vulnerability intelligence.

SQL injection vulnerability in Md Yeasin Ul Haider URL Shortener (exact-links) plugin versions up to 3.0.7 allows unauthenticated attackers to execute arbitrary SQL queries against the underlying database. The vulnerability stems from improper sanitization of user-supplied input in SQL commands, enabling data exfiltration, modification, or deletion depending on database permissions. Actively exploited status unknown, though the issue affects a WordPress plugin with broad installation base; EPSS probability is low at 0.05% percentile, suggesting limited real-world exploitation despite technical severity.

Blind SQL injection in CMSJunkie WP-BusinessDirectory WordPress plugin versions up to 3.1.4 allows unauthenticated remote attackers to execute arbitrary SQL queries against the plugin's database. This vulnerability, reported by Patchstack, enables attackers to extract sensitive data or manipulate database contents without direct visibility into query results, posing a significant risk to WordPress installations using affected versions.

SQL injection in YayCommerce SMTP for Amazon SES WordPress plugin through version 1.9 allows authenticated attackers to execute arbitrary SQL queries against the site database. The vulnerability exists in the plugin's improper handling of user input in SQL commands, enabling data exfiltration, modification, or deletion. Although no CVSS vector or public exploit code has been published, the low EPSS score (0.05%, 15th percentile) suggests limited practical exploitation despite the vulnerability's presence in an actively maintained plugin.

SQL injection in QuanticaLabs GymBase Theme Classes WordPress plugin versions up to 1.4 enables unauthenticated remote attackers to execute arbitrary SQL queries against the underlying database. The vulnerability exists in the gymbase_classes component and carries an EPSS score of 0.05% (16th percentile), indicating very low exploitation probability despite the critical nature of SQL injection flaws. No public exploit code or active exploitation has been identified at the time of analysis.

SQL injection vulnerability in YayCommerce SMTP for SendGrid (YaySMTP) WordPress plugin version 1.5 and earlier allows authenticated attackers to execute arbitrary SQL commands against the plugin's database queries. The vulnerability enables data exfiltration, modification, or deletion depending on database permissions. EPSS score of 0.05% indicates low exploitation probability despite the SQL injection classification.

SQL injection vulnerability in YayCommerce YayExtra WordPress plugin up to version 1.5.5 allows unauthenticated remote attackers to execute arbitrary SQL commands against the underlying database. The flaw stems from improper sanitization of user-supplied input in SQL queries, enabling database enumeration, data exfiltration, or potential privilege escalation. No public exploit code or active exploitation has been confirmed at time of analysis, though the low EPSS score (0.05%) suggests minimal real-world attack activity despite the vulnerability's technical severity.

SQL injection vulnerability in YayCommerce YaySMTP WordPress plugin through version 1.3 allows attackers to execute arbitrary SQL commands against the plugin's database queries. The vulnerability affects the smtp-sendinblue plugin and has been reported by Patchstack security researchers; however, no public exploit code or confirmed active exploitation has been identified at this time. With an EPSS score of 0.05% (15th percentile), this represents a low exploitation probability despite the critical nature of SQL injection vulnerabilities.

WeGIA versions prior to 3.4.5 contain a SQL Injection vulnerability in the member deletion endpoint that allows authenticated users to execute arbitrary SQL commands via the `id_socio` parameter. This high-severity vulnerability (CVSS 8.8) compromises the confidentiality, integrity, and availability of the entire database. The vulnerability requires valid credentials to exploit but offers complete database compromise once authenticated.

CVE-2025-53639 is a critical SQL injection vulnerability in MeterSphere's API sorting functionality where the sortField parameter lacks proper input validation and sanitization. All versions prior to 3.6.5-lts are affected, allowing unauthenticated remote attackers to execute arbitrary SQL statements and completely compromise database integrity, availability, and confidentiality. This is a network-exploitable vulnerability with no authentication required and high real-world risk.

SemCms v5.0 was discovered to contain a SQL injection vulnerability via the lgid parameter at SEMCMS_Products.php.

SemCms v5.0 was discovered to contain a SQL injection vulnerability via the ID parameter at SEMCMS_Products.php.

SemCms v5.0 was discovered to contain a SQL injection vulnerability via the ID parameter at SEMCMS_InquiryView.php.

SemCms v5.0 was discovered to contain a SQL injection vulnerability via the lgid parameter at SEMCMS_Link.php.

SemCms v5.0 was discovered to contain a SQL injection vulnerability via the ID parameter at SEMCMS_Link.php.

SemCms v5.0 was discovered to contain a SQL injection vulnerability via the pid parameter at SEMCMS_Quanxian.php.

SemCms v5.0 was discovered to contain a SQL injection vulnerability via the pid parameter at SEMCMS_Infocategories.php.

SemCms v5.0 was discovered to contain a SQL injection vulnerability via the pid parameter at SEMCMS_ct.php.

SemCms v5.0 was discovered to contain a SQL injection vulnerability via the pid parameter at SEMCMS_Categories.php.

CVE-2025-7612 is a critical SQL injection vulnerability in code-projects Mobile Shop 1.0 affecting the /login.php file's email parameter, allowing remote unauthenticated attackers to execute arbitrary SQL queries and potentially extract or modify sensitive data. The vulnerability has been publicly disclosed with exploit code available, making it actively exploitable in the wild. With a CVSS score of 7.3 and demonstrated public PoC availability, this represents an immediate threat to deployments of this product.

CVE-2025-7611 is a critical SQL injection vulnerability in code-projects Wedding Reservation version 1.0, affecting the /global.php file's 'lu' parameter. Remote unauthenticated attackers can exploit this to execute arbitrary SQL queries, potentially leading to unauthorized data access, modification, or deletion. The vulnerability has been publicly disclosed with exploit code available, significantly increasing real-world exploitation risk.

CVE-2025-7610 is a critical SQL injection vulnerability in code-projects Electricity Billing System 1.0 affecting the password change functionality at /user/change_password.php. An unauthenticated remote attacker can inject arbitrary SQL commands through the new_password parameter to read, modify, or delete database contents. The vulnerability has been publicly disclosed with proof-of-concept code available, making active exploitation highly probable.

CVE-2025-7609 is a critical SQL injection vulnerability in code-projects Simple Shopping Cart 1.0 affecting the /register.php endpoint via the ruser_email parameter. An unauthenticated remote attacker can exploit this to read, modify, or delete database contents, potentially compromising user data and application integrity. Public exploit code exists, increasing real-world exploitation risk.

CVE-2025-7608 is a critical SQL injection vulnerability in code-projects Simple Shopping Cart 1.0 affecting the /userlogin.php endpoint's user_email parameter, allowing unauthenticated remote attackers to execute arbitrary SQL queries and potentially extract, modify, or delete database contents. The vulnerability has been publicly disclosed with proof-of-concept exploit code available, and while the CVSS score is 7.3 (moderate-to-high severity), the low attack complexity and lack of authentication requirements make this a high-priority exploit target for threat actors.

CVE-2025-7607 is a critical SQL injection vulnerability in code-projects Simple Shopping Cart 1.0 affecting the /Customers/save_order.php file, where the order_price parameter is improperly sanitized, allowing remote unauthenticated attackers to execute arbitrary SQL queries. The vulnerability has a public exploit disclosure and carries a CVSS score of 7.3 with demonstrated real-world exploitation potential, making it a high-priority security concern for affected deployments.

CVE-2025-7606 is a critical SQL injection vulnerability in code-projects AVL Rooms 1.0 affecting the /city.php file, where the 'city' parameter is improperly sanitized, allowing remote unauthenticated attackers to execute arbitrary SQL queries. The vulnerability has a CVSS score of 7.3 (High) with confirmed public exploit disclosure and active exploitation potential, enabling attackers to read, modify, or delete database contents without authentication.

CVE-2025-7605 is a critical SQL injection vulnerability in code-projects AVL Rooms 1.0 affecting the /profile.php endpoint via the first_name parameter. An unauthenticated remote attacker can exploit this to execute arbitrary SQL queries, potentially leading to unauthorized data access, modification, or system compromise. Public exploit code is available and the vulnerability is likely to be actively exploited given its network-accessible nature, low attack complexity, and lack of authentication requirements.