CVE-2025-6005VulnerabilityPublished 12 Jun 2025

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

Affects kiCode111 like-girlSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 07:57 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: 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-26.

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
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

1. Immediate mitigation should include restricting access to the /admin/aboutPost.php endpoint to trusted internal networks or VPN users only, minimizing exposure to untrusted actors. 2. Implement Web Application Firewall (WAF) rules specifically targeting SQL injection patterns on the affected parameters to block malicious payloads. 3. Conduct thorough input validation and sanitization on all parameters listed, using parameterized queries or prepared statements to prevent injection. 4. If possible, upgrade to a newer, patched version of like-girl once available or consider alternative products if vendor support is discontinued. 5. Monitor application logs for unusual database query patterns or errors indicative of injection attempts. 6. Employ network segmentation to isolate administrative interfaces from general user access. 7. Regularly back up databases to enable recovery in case of data corruption or loss. 8. Engage in proactive threat hunting and vulnerability scanning focused on this CVE to detect exploitation attempts early. 9. If vendor patches remain unavailable, consider code review and custom patching by internal security teams or third-party experts to remediate the vulnerability.

Description

A vulnerability classified as critical was found in kiCode111 like-girl 5.2.0. This vulnerability affects unknown code of the file /admin/aboutPost.php. The manipulation of the argument title/aboutimg/info1/info2/info3/btn1/btn2/infox1/infox2/infox3/infox4/infox5/infox6/btnx2/infof1/infof2/infof3/infof4/btnf3/infod1/infod2/infod3/infod4/infod5 leads to sql injection. The attack can be initiated 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 5.2.0, this vulnerability poses a risk of unauthorized database access or manipulation. Successful exploitation could lead to data leakage, unauthorized data modification, or disruption of application functionality. Although the CVSS score is medium, the fact that exploitation requires high privileges limits the attacker's initial access vector, potentially reducing the risk to internal or less exposed systems. However, if an attacker gains administrative access or if the application is misconfigured to allow broader access, the impact could escalate. Data confidentiality and integrity could be compromised, affecting sensitive business or customer information. Availability impact is low but could occur if injected queries cause application errors or crashes. The lack of vendor patching means organizations must rely on compensating controls. Given the public disclosure, European entities in sectors with high regulatory requirements (e.g., finance, healthcare) could face compliance risks if data breaches occur. Additionally, organizations with internet-facing administrative interfaces are at higher risk of remote exploitation.

Summary

CVE-2025-6005 is a SQL Injection vulnerability identified in kiCode111's product "like-girl" version 5.2.0, specifically within the /admin/aboutPost.php file. The vulnerability arises from improper sanitization or validation of multiple input parameters including title, aboutimg, info1 through info6, btn1, btn2, infox1 through infox6, btnx2, infof1 through infof4, btnf3, and infod1 through infod5. An attacker can remotely manipulate these parameters to inject malicious SQL code, potentially altering the backend database queries executed by the application. The vulnerability does not require user interaction or authentication, making it remotely exploitable over the network. Despite the critical classification, the CVSS 4.0 score is 5.1 (medium severity) due to the presence of high privileges required (PR:H) and limited impact on confidentiality, integrity, and availability (all low). The vendor has not responded to disclosure attempts, and no patches or mitigations have been published. No known exploits are currently reported in the wild, but public disclosure increases the risk of exploitation attempts. The vulnerability affects only version 5.2.0 of the product, and the lack of vendor response suggests that organizations using this version remain exposed. The attack surface is broad given the numerous parameters vulnerable to injection, increasing the likelihood of successful exploitation if the application is internet-facing or accessible by untrusted users.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Jun 2025, 01:38 UTC

Technical details

References

Community reviews

Related threats