Local Services Search Engine Management System
Monthly
We need to produce a JSON analysis for CVE-2025-8179. The instructions require a thorough, multi-source synthesis. Input data: description, CVSS 4.0 vector (no 3.1 provided, so we'll need to assess CVSS 3.1 independently), CWE-74 (Injection), EPSS 0.07% (percentile 20%, low), POC publicly available (exploit disclosed), no KEV mention so not actively exploited yet. CPE string: cpe:2.3:a:phpgurukul:local_services_search_engine_management_system:2.1:*:*:*:*:*:*:*. Tags: SQLi, PHP, Local Services Search Engine Management System. References: GitHub exploit, vendor site, VulDB. Product name: "Local Services Search Engine Management System" is the full product name from CPE and description. But must be 1-3 words ONLY. "Local Services Search Engine Management System" too long. Could be "Local Services Search Engine" or simpler "Local Services Search Engine Management System"? The instruction: "1-3 words ONLY. The specific product or service name affected." It's a software system. Could say "Local Services Search Engine" but maybe just "PHPGurukul LMS"? CPE says phpgurukul:local_services_search_engine_management_system. I'll choose "Local Services Search Engine MS" still too many words. "Local Services Search Engine" is 4 words. Hmm. Perhaps "PHPGurukul Local Services" or just "Local Services Search"? The product is a Management System. Maybe "Local Services Search Engine Management System" is a proper name, but 4 words. I'll go with "Local Services Search Engine" (4 words, still violate). Need to be 3 words. Could think of acronym? Not recommended. The description: "PHPGurukul Local Services Search Engine Management System 2.1" - the system name is "Local Services Search Engine Management System", but if I take "Local Services Search" (3 words). But "Search Engine" might be core. Another approach: use "PHPGurukul Local Services" (vendor+product). However, the vulnerability is in the "Local Services Search Engine Management System". I'll pick "Local Services Search Engine"
SQL injection in PHPGurukul Local Services Search Engine Management System 2.1 enables remote unauthenticated attackers to inject arbitrary SQL commands via the editid parameter in /admin/edit-category-detail.php, potentially allowing unauthorized database access or modification. A publicly available proof-of-concept exists, but real-world exploitation remains minimal with EPSS at 0.06% (18th percentile), indicating the vulnerable application has extremely limited deployment footprint despite the publicly disclosed vulnerability.
Critical SQL injection vulnerability in PHPGurukul Local Services Search Engine Management System version 2.1, specifically in the /admin/edit-person-detail.php file where the 'editid' parameter is not properly sanitized. 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 public exploit code available and may be actively exploited in the wild.
A vulnerability was found in PHPGurukul Local Services Search Engine Management System 1.0 and classified as critical.php. Rated medium severity (CVSS 6.9), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
A persistent cross-site scripting vulnerability was discovered in Local Services Search Engine Management System Project 1.0 which allows remote attackers to execute arbitrary code via crafted. Rated medium severity (CVSS 4.8), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
A SQL injection vulnerability was discovered in the editid parameter in Local Services Search Engine Management System Project 1.0. Rated medium severity (CVSS 4.9), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
Local Service Search Engine Management System 1.0 has a vulnerability through authentication bypass using SQL injection . Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
We need to produce a JSON analysis for CVE-2025-8179. The instructions require a thorough, multi-source synthesis. Input data: description, CVSS 4.0 vector (no 3.1 provided, so we'll need to assess CVSS 3.1 independently), CWE-74 (Injection), EPSS 0.07% (percentile 20%, low), POC publicly available (exploit disclosed), no KEV mention so not actively exploited yet. CPE string: cpe:2.3:a:phpgurukul:local_services_search_engine_management_system:2.1:*:*:*:*:*:*:*. Tags: SQLi, PHP, Local Services Search Engine Management System. References: GitHub exploit, vendor site, VulDB. Product name: "Local Services Search Engine Management System" is the full product name from CPE and description. But must be 1-3 words ONLY. "Local Services Search Engine Management System" too long. Could be "Local Services Search Engine" or simpler "Local Services Search Engine Management System"? The instruction: "1-3 words ONLY. The specific product or service name affected." It's a software system. Could say "Local Services Search Engine" but maybe just "PHPGurukul LMS"? CPE says phpgurukul:local_services_search_engine_management_system. I'll choose "Local Services Search Engine MS" still too many words. "Local Services Search Engine" is 4 words. Hmm. Perhaps "PHPGurukul Local Services" or just "Local Services Search"? The product is a Management System. Maybe "Local Services Search Engine Management System" is a proper name, but 4 words. I'll go with "Local Services Search Engine" (4 words, still violate). Need to be 3 words. Could think of acronym? Not recommended. The description: "PHPGurukul Local Services Search Engine Management System 2.1" - the system name is "Local Services Search Engine Management System", but if I take "Local Services Search" (3 words). But "Search Engine" might be core. Another approach: use "PHPGurukul Local Services" (vendor+product). However, the vulnerability is in the "Local Services Search Engine Management System". I'll pick "Local Services Search Engine"
SQL injection in PHPGurukul Local Services Search Engine Management System 2.1 enables remote unauthenticated attackers to inject arbitrary SQL commands via the editid parameter in /admin/edit-category-detail.php, potentially allowing unauthorized database access or modification. A publicly available proof-of-concept exists, but real-world exploitation remains minimal with EPSS at 0.06% (18th percentile), indicating the vulnerable application has extremely limited deployment footprint despite the publicly disclosed vulnerability.
Critical SQL injection vulnerability in PHPGurukul Local Services Search Engine Management System version 2.1, specifically in the /admin/edit-person-detail.php file where the 'editid' parameter is not properly sanitized. 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 public exploit code available and may be actively exploited in the wild.
A vulnerability was found in PHPGurukul Local Services Search Engine Management System 1.0 and classified as critical.php. Rated medium severity (CVSS 6.9), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
A persistent cross-site scripting vulnerability was discovered in Local Services Search Engine Management System Project 1.0 which allows remote attackers to execute arbitrary code via crafted. Rated medium severity (CVSS 4.8), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
A SQL injection vulnerability was discovered in the editid parameter in Local Services Search Engine Management System Project 1.0. Rated medium severity (CVSS 4.9), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
Local Service Search Engine Management System 1.0 has a vulnerability through authentication bypass using SQL injection . Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.