CVE-2025-14637VulnerabilityPublished 13 Dec 2025Updated 15 Dec 2025

CVE-2025-14637: itsourcecode Online Pet Shop Management System · SQL Injection

Affects itsourcecode Online Pet Shop Management SystemSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
itsourcecode Online Pet Shop Management System	Affected =1.0	Fixed in–

AI-suggested

1. Immediate application of vendor patches or updates once released is the most effective mitigation. Monitor vendor channels for patch announcements. 2. In the absence of patches, implement strict input validation and sanitization on the 'cnpname' parameter and all user inputs, using allowlists and rejecting suspicious characters. 3. Refactor the affected code to use parameterized queries or prepared statements to prevent SQL injection. 4. Deploy Web Application Firewalls (WAFs) configured to detect and block SQL injection patterns targeting the vulnerable endpoint. 5. Conduct regular security assessments and code reviews focusing on input handling and database interactions. 6. Monitor logs for unusual database queries or errors indicative of injection attempts. 7. Educate developers on secure coding practices to prevent similar vulnerabilities in future releases. 8. Restrict database user permissions to the minimum necessary to limit the impact of any successful injection. 9. Backup databases regularly and verify the integrity of backups to enable recovery in case of data corruption. 10. Consider network segmentation to isolate vulnerable systems and reduce exposure.

Description

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.

Impact

For European organizations, the impact of this SQL injection vulnerability can be significant, particularly for small and medium enterprises (SMEs) operating pet shop management or similar e-commerce platforms using the affected software. Successful exploitation could lead to unauthorized access to customer data, including personal and payment information, resulting in data breaches and regulatory non-compliance under GDPR. Integrity of the database could be compromised, allowing attackers to alter product listings, pricing, or transaction records, potentially causing financial losses and reputational damage. Availability impacts could disrupt business operations if the database is corrupted or taken offline. Given the medium severity, the threat is moderate but non-negligible, especially as the exploit requires no authentication and can be launched remotely. Organizations lacking robust security controls or monitoring may be more vulnerable to exploitation. The public availability of exploit code increases the risk of opportunistic attacks, including by cybercriminals targeting smaller businesses with limited cybersecurity resources.

Summary

CVE-2025-14637 identifies a SQL injection vulnerability in the itsourcecode Online Pet Shop Management System version 1.0, specifically in the /pet1/addcnp.php script. The vulnerability arises from insufficient input validation or sanitization of the 'cnpname' parameter, which is directly used in SQL queries without proper escaping or parameterization. This allows an unauthenticated remote attacker to inject arbitrary SQL commands, potentially manipulating the backend database. The vulnerability is exploitable over the network without any user interaction, making it highly accessible to attackers. The CVSS 4.0 base score of 6.9 reflects a medium severity, considering the attack vector is network-based with low complexity and no privileges required, but with limited impact on confidentiality, integrity, and availability (each rated low). The vulnerability could allow attackers to read, modify, or delete data, or disrupt service availability depending on the database permissions and structure. Although no confirmed exploits are currently active in the wild, the public availability of exploit code increases the likelihood of attacks. The lack of vendor patches at the time of reporting necessitates immediate mitigation steps by users. This vulnerability highlights the critical importance of secure coding practices, especially input validation and use of parameterized queries in web applications handling sensitive data.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 20 Dec 2025, 20:07 UTC

Technical details

References

Community reviews

Related threats