VulnerabilityPublished 28 Dec 2025Updated 29 Dec 2025

CVE-2025-15142: 9786 phpok3w · SQL Injection

Affects 9786 phpok3wSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 09:15 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 23% 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 28 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 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 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

AI-suggested

1. Implement immediate input validation and sanitization for the ID parameter in show.php, ensuring all inputs are strictly validated against expected formats and lengths. 2. Refactor the vulnerable code to use parameterized queries or prepared statements to prevent SQL injection. 3. Deploy Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting the ID parameter. 4. Monitor web server and database logs for suspicious activities indicative of SQL injection attempts. 5. Restrict database user privileges to the minimum necessary to limit the impact of a successful injection. 6. If possible, isolate the phpok3w application environment to reduce lateral movement risks. 7. Engage with the vendor or community to track patch releases or official fixes and apply them promptly once available. 8. Conduct security audits and penetration testing focusing on injection vulnerabilities in the application. 9. Educate development teams on secure coding practices to prevent similar vulnerabilities in future rolling releases.

Description

A vulnerability was identified in 9786 phpok3w up to 901d96a06809fb28b17f3a4362c59e70411c933c. Impacted is an unknown function of the file show.php. The manipulation of the argument ID leads to sql injection. It is possible to initiate the attack remotely. The exploit is publicly available and might be used. This product is using a rolling release to provide continious delivery. Therefore, no version details for affected nor updated releases are available. The project was informed of the problem early through an issue report but has not responded yet.

Impact

For European organizations, this vulnerability can lead to unauthorized access to sensitive data, including personal, financial, or operational information stored in databases managed by phpok3w. Attackers exploiting this flaw could manipulate or delete data, disrupt services, or use the compromised system as a foothold for further attacks within the network. This is particularly concerning for sectors such as finance, healthcare, government, and e-commerce, where data integrity and confidentiality are paramount. The remote and unauthenticated nature of the exploit increases the risk of widespread attacks, potentially leading to regulatory non-compliance under GDPR due to data breaches. Additionally, service disruptions could impact business continuity and reputation. The lack of an official patch necessitates immediate mitigation efforts to reduce exposure.

Summary

CVE-2025-15142 is a SQL injection vulnerability identified in the 9786 phpok3w web application, specifically within the show.php script. The vulnerability arises from improper sanitization of the ID parameter, allowing an attacker to inject malicious SQL queries remotely without requiring authentication or user interaction. This flaw can lead to unauthorized data disclosure, modification, or deletion, compromising the confidentiality, integrity, and availability of the backend database. Although no active exploitation in the wild has been reported, public exploit code exists, increasing the likelihood of attacks. The vulnerability has a CVSS 4.0 base score of 6.9, reflecting medium severity due to its network attack vector, lack of required privileges or user interaction, and partial impact on data confidentiality, integrity, and availability. The vendor has been notified but has not yet responded or provided a fix. This vulnerability poses a significant risk to any organization using phpok3w, especially those hosting sensitive data or critical services.

References

Community reviews

Loading reviews…