CVE-2025-14643
BaseFortify
Publication date: 2025-12-14
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 |
|---|---|---|
| fabian | simple_attendance_record_system | 2.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is an SQL injection found in the Simple Attendance Record System 2.0, specifically in an unknown function within the /check.php file. By manipulating the 'student' argument, an attacker can inject malicious SQL code. This vulnerability can be exploited remotely and the exploit code has been made public.
How can this vulnerability impact me? :
The vulnerability allows remote attackers to perform SQL injection, which can lead to unauthorized access to or modification of the database. This can result in data leakage, data corruption, or loss of data integrity, potentially compromising the confidentiality, integrity, and availability of the system's data.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking for the presence of the vulnerable 'check.php' file in the code-projects Simple Attendance Record System 2.0 and testing the 'student' parameter for SQL injection. One detection method is to use Google dorking with queries such as 'inurl:check.php' to identify potentially vulnerable targets. Additionally, manual testing can be performed by sending crafted HTTP POST requests to the 'check.php' endpoint with SQL injection payloads in the 'student' parameter, such as ' OR 1=1-- or ' UNION SELECT statements. Network monitoring tools can also be used to detect suspicious SQL injection attempts targeting this parameter. Specific commands for testing might include curl commands like: curl -X POST -d "student=' OR 1=1--" http://target/check.php [3, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected software with an alternative product, as no known countermeasures or mitigations currently exist for this vulnerability. Additionally, restricting access to the vulnerable 'check.php' file, applying web application firewalls (WAF) to block SQL injection payloads, and monitoring for suspicious activity can help reduce risk. It is also recommended to avoid using the vulnerable version 2.0 of the Simple Attendance Record System until a patched version or alternative is available. [3]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not explicitly discuss the impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA. However, since the vulnerability allows remote SQL injection leading to potential data leakage of sensitive information (e.g., password hashes, private exam information), it could result in unauthorized access to personal or sensitive data, which may violate data protection regulations like GDPR or HIPAA. Nonetheless, no direct statements or analyses regarding compliance impact are given. [2, 3]