CVE-2025-14587
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-12-13

Last updated on: 2026-04-29

Assigner: VulDB

Description
A vulnerability was identified in itsourcecode Online Pet Shop Management System 1.0. This affects an unknown part of the file /pet1/available.php. Such manipulation of the argument Name leads to sql injection. The attack can be executed remotely. The exploit is publicly available and might be used.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-13
Last Modified
2026-04-29
Generated
2026-05-07
AI Q&A
2025-12-13
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
facebook-riares online_pet_shop_management_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 Powered Q&A
Can you explain this vulnerability to me?

This vulnerability is a SQL injection in the itsourcecode Online Pet Shop Management System 1.0, specifically in the /pet1/available.php file. An attacker can manipulate the 'Name' argument remotely to execute unauthorized SQL commands on the database.


How can this vulnerability impact me? :

The vulnerability can allow an attacker to remotely execute SQL injection attacks, potentially leading to unauthorized access, data leakage, data modification, or disruption of the application's normal operation.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The vulnerability allows unauthorized access, modification, and exposure of sensitive data due to SQL injection, which can lead to breaches of confidentiality, integrity, and availability of data. Such data breaches can result in non-compliance with common standards and regulations like GDPR and HIPAA, which mandate protection of personal and sensitive information. Therefore, exploitation of this vulnerability could cause violations of these regulations by exposing or compromising protected data. [1, 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 /pet1/available.php endpoint for SQL injection via the 'name' parameter using SQL injection testing tools such as sqlmap. For example, you can use the following command to test the vulnerability: sqlmap -u "http://targetsite/pet1/available.php" --data="name=test&foodid=1&address=addr&contact=123&oqty=1&otype=type&datep=2025-01-01&savechanges=1" --method=POST --risk=3 --level=5 Additionally, Google dorking can be used to identify potentially vulnerable targets with queries like: inurl:pet1/available.php These methods help identify if the 'name' parameter is vulnerable to SQL injection by observing responses or behavior changes indicating injection success. [1, 2]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include: - Implement prepared statements with parameter binding to separate SQL code from user input. - Enforce strict input validation and filtering to ensure data conforms to expected formats. - Minimize database user permissions by avoiding use of high-privilege accounts such as 'root' or 'admin' for application operations. - Conduct regular security audits to detect and address vulnerabilities promptly. - Consider replacing the affected product with an alternative solution if remediation is not feasible. These steps help prevent exploitation by ensuring that user input cannot manipulate SQL queries and by limiting the potential impact of any successful injection. [2, 1, 3]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart