VulnerabilityPublished 12 Jun 2025

CVE-2025-6007: kiCode111 like-girl · SQL Injection

Affects kiCode111 like-girlSource CVE Database V5

Public exploit available · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score

5.1Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/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: High
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: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
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 12 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

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 or the CVSS exploit maturity 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
GitHubkicode111/like-girl`pkg:github/kicode111/like-girl`Other threats	Affected =5.2.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Immediate mitigation should involve restricting access to the /admin/CopyadminPost.php endpoint via network controls such as IP whitelisting, VPN-only access, or web application firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting the 'icp/Copyright' parameter.
Conduct thorough input validation and sanitization on all parameters, especially those used in SQL queries, employing parameterized queries or prepared statements to prevent injection.
Monitor application logs and database query logs for unusual or suspicious activity indicative of SQL injection attempts.
If possible, upgrade to a later, patched version of like-girl once available or apply vendor-provided patches promptly.
In the absence of vendor patches, consider isolating the affected application in a segmented network zone to limit potential lateral movement.
Perform regular security assessments and penetration testing focused on injection vulnerabilities.
Educate administrators and developers about secure coding practices and the risks of SQL injection.
Implement database-level restrictions such as least privilege for the application database user to minimize damage from potential exploitation.

Description

A vulnerability, which was classified as critical, was found in kiCode111 like-girl 5.2.0. Affected is an unknown function of the file /admin/CopyadminPost.php. The manipulation of the argument icp/Copyright leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations using kiCode111 like-girl version 5.2.0, this vulnerability poses a moderate risk primarily to the confidentiality and integrity of their data. Exploitation could allow attackers to extract sensitive information, modify or delete data, or potentially escalate privileges within the application’s database. Given the vulnerability is remotely exploitable without authentication, attackers could target exposed administrative interfaces, leading to unauthorized access to backend systems. The impact is somewhat mitigated by the low CVSS score, indicating limited scope and impact; however, organizations with critical data or regulatory compliance requirements (e.g., GDPR) could face significant legal and reputational consequences if data is compromised. Additionally, the lack of vendor remediation increases exposure time. The threat is particularly relevant for sectors relying on this software for administrative or content management functions, including SMEs and niche service providers in Europe. The absence of known exploits in the wild reduces immediate risk but does not eliminate the potential for future attacks, especially given public exploit disclosure.

Summary

CVE-2025-6007 is a SQL Injection vulnerability identified in version 5.2.0 of the kiCode111 like-girl web application, specifically within an unspecified function in the /admin/CopyadminPost.php file. The vulnerability arises from improper sanitization or validation of the 'icp/Copyright' parameter, which can be manipulated by an attacker to inject malicious SQL commands. This flaw allows remote attackers to execute arbitrary SQL queries on the backend database without requiring authentication or user interaction. Although the vendor was notified early, no response or patch has been issued, and while no known exploits are currently observed in the wild, the exploit code has been publicly disclosed. The vulnerability has been assigned a CVSS v4.0 base score of 5.1, categorized as medium severity, reflecting a network attack vector with low complexity and no required privileges or user interaction. The impact on confidentiality, integrity, and availability is rated low, indicating limited potential for severe damage or data leakage under typical conditions. However, the presence of a SQL Injection in an administrative endpoint suggests potential for unauthorized data access or modification if exploited effectively. The lack of vendor response and patch availability increases the risk for organizations using this specific version of the product.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Jun 2025, 02:23 UTC

Technical details

References

Community reviews

Related threats