PHP
CVE-2025-14637
MEDIUM
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
2DescriptionCVE.org
A weakness has been identified in itsourcecode Online Pet Shop Management System 1.0. This vulnerability affects unknown code of the file /pet1/addcnp.php. This manipulation of the argument cnpname causes sql injection. The attack can be initiated remotely. The exploit has been made available to the public and could be exploited.
AnalysisAI
We need to produce a comprehensive JSON analysis for CVE-2025-14637. Let's go through each field carefully using the provided data.
Product name: The affected product is "Online Pet Shop Management System" from itsourcecode. The CPE indicates the product is "online_pet_shop_management_system" version 1.0. The name should be short: "Online Pet Shop Management System" is a bit long; it's okay to use "Online Pet Shop Management System" but the instruction says "1-3 words ONLY". So we need a concise name: maybe "Pet Shop Management System"? Or "Online Pet Shop"? The CPE product field is "online_pet_shop_management_system". Let's use "Pet Shop Management System". That is 4 words? "Pet Shop Management System" is 4 words. The instruction says 1-3 words. Maybe "Online Pet Shop"? That's 3 words but lacks "Management". However, the vulnerability is in the admin panel and it's a management system. Since the description says "Online Pet Shop Management System", I'll use "Pet Shop Management System" but that's 4. Alternatively, "PetShop Management" is 2 words. But let's keep it as "Online Pet Shop" as 3 words. The CPE is "online_pet_shop_management_system" - perhaps "Online Pet Shop" is sufficient.
But the instruction says "1-3 words ONLY" and "Examples: 'Apache Tomcat', 'WordPress', 'Linux Kernel', 'nginx-ui', 'GoAnywhere MFT'." So it's fine to use a shorter name like "Pet Shop Management"? Actually "Management" is one word. "Pet Shop Management" is 3 words. That's acceptable. I'll use "Pet Shop Management System" (4) - that's too many. Let's see: "Online Pet Shop" is 3 words and captures the product. However, the vulnerability is specifically in the management system. The CPE has "online_pet_shop_management_system". I think "Pet Shop Management" is fine as 3 words. I'll go with "Pet Shop Management".
Summary: Need 2-3 sentence plain-language summary. Must not start with "A vulnerability". Start with impact verb and product. Example: "SQL injection in Online Pet Shop Managem
In PHP versions 7.1.x below 7.1.33, 7.2.x below 7.2.24 and 7.3.x below 7.3.11 in certain configurations of FPM setup it
sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not
(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear
The '/common/download_agent_installer.php' script in the Quest KACE System Management Appliance 8.0.318 is accessible by
ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Rated critical severity (C
Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au
Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 allows remote attackers to execute arbitrary PHP c
Palo Alto Networks PAN-OS management web interface contains an authentication bypass allowing unauthenticated attackers
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
The get_referers function in /opt/ws/bin/sblistpack in Sophos Web Appliance before 3.7.9.1 and 3.8 before 3.8.1.1 allows
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
Share
External POC / Exploit Code
Leaving vuln.today