CVE-2025-14939
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-12-19

Last updated on: 2026-04-29

Assigner: VulDB

Description
A vulnerability was found in code-projects Online Appointment Booking System 1.0. Impacted is an unknown function of the file /admin/deletemanager.php. The manipulation of the argument managername results in sql injection. The attack may be performed from remote. The exploit has been made public and could be used.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-19
Last Modified
2026-04-29
Generated
2026-06-16
AI Q&A
2025-12-19
EPSS Evaluated
2026-06-15
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
anisha online_appointment_booking_system 1.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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 Quick Actions
Instant insights powered by AI
Executive Summary

CVE-2025-14939 is a critical SQL injection vulnerability in version 1.0 of the Online Appointment Booking System, specifically in the /admin/deletemanager.php file. It occurs because the 'managername' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This can alter the intended SQL queries executed by the system, potentially leading to unauthorized database access and manipulation. [1, 2, 3]

Impact Analysis

This vulnerability can impact you by allowing attackers to remotely exploit the system to access, modify, or delete sensitive data in the database. It can lead to unauthorized database access, data leakage, data modification or deletion, full system compromise, and potential service disruption. The attack can affect the confidentiality, integrity, and availability of the system. [1, 2, 3]

Detection Guidance

This vulnerability can be detected by checking for the presence of the vulnerable endpoint `/admin/deletemanager.php` and testing the `managername` parameter for SQL injection. One method is to use Google dorking with the query `inurl:admin/deletemanager.php` to identify potentially vulnerable targets. For active testing, tools like sqlmap can be used to test the parameter for SQL injection vulnerabilities. Example sqlmap command: `sqlmap -u "http://target/admin/deletemanager.php?managername=admin" --batch --dbms=mysql` which automates detection of SQL injection. Additionally, manual testing can involve injecting payloads such as `' OR 1=1--` or time-based payloads using `SLEEP()` functions to observe delays indicating SQL injection. [1, 2]

Mitigation Strategies

Immediate mitigation steps include: 1) Replacing the affected component or upgrading to a version without this vulnerability if available. 2) Implementing prepared statements with parameter binding to separate SQL code from user input, preventing injection. 3) Applying strict input validation and filtering on the `managername` parameter to ensure it conforms to expected formats. 4) Minimizing database user permissions by avoiding use of high-privilege accounts for routine operations. 5) Conducting regular security audits to detect and remediate vulnerabilities promptly. Since no known countermeasures are documented, replacing the vulnerable component is strongly suggested. [1, 2]

Compliance Impact

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 unauthorized database access, data leakage, and modification, it could potentially lead to violations of data protection requirements under such regulations by compromising confidentiality, integrity, and availability of sensitive data. No direct statements about compliance impact or regulatory consequences are given. [1, 2, 3]

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-14939. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart