CVE-2025-6321
BaseFortify
Publication date: 2025-06-20
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| phpgurukul | pre-school_enrollment_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-6321 is a critical SQL injection vulnerability in the PHPGurukul Pre-School Enrollment System version 1.0. It exists in the /admin/add-subadmin.php file, specifically in the sadminusername parameter. This parameter is used directly in SQL queries without proper sanitization or validation, allowing attackers to inject malicious SQL code. This enables unauthorized manipulation of SQL commands, potentially leading to unauthorized database access, data leakage, data manipulation, and full system compromise. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can be exploited remotely without authentication, making it highly accessible. Attackers can manipulate SQL queries to perform unauthorized database operations, which can lead to data leakage, data manipulation, and potentially full system compromise. This threatens the confidentiality, integrity, and availability of the system, impacting system security and business continuity. [2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the /admin/add-subadmin.php endpoint for SQL injection via the sadminusername parameter. A proof-of-concept payload involves injecting a time-based SQL command such as: sadminusername=AAA'+RLIKE+SLEEP(10)+AND+'tOHP'='tOHP. You can perform a crafted POST request to /preschool/admin/add-subadmin.php with this payload and observe if the response is delayed, indicating SQL injection. Additionally, attackers may be identified by searching for the vulnerable URL pattern using Google dorking with queries like "inurl:admin/add-subadmin.php". [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Replacing the affected component with an alternative product if possible, as no known countermeasures are documented. 2) Implementing prepared statements with parameter binding to prevent SQL injection. 3) Applying strict input validation and filtering on the sadminusername parameter. 4) Limiting database user permissions to the minimum necessary, avoiding high-privilege accounts for routine operations. [2, 3]