CVE-2025-15142
SQL Injection in phpok3w show.php Allows Remote Exploitation
Publication date: 2025-12-28
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| phpok3w | phpok3w | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a SQL injection in the file show.php of the phpok3w project. It occurs due to manipulation of the argument ID, allowing an attacker to inject malicious SQL code. The attack can be initiated remotely, and an exploit is publicly available.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not explicitly discuss the impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA. However, since the vulnerability allows unauthorized access to sensitive database information through SQL injection, it could potentially lead to data breaches that violate data protection regulations. No direct statements about compliance impact or mitigation in relation to these standards are given. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'id' GET parameter in the show.php file for SQL injection. Tools like sqlmap can be used to verify the injection capability. Additionally, attackers may identify vulnerable targets using Google dorking with queries such as 'inurl:show.php'. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
No known countermeasures or patches currently exist for this vulnerability. Immediate mitigation steps include considering replacing the affected phpok3w component with an alternative product. Since the vendor has not responded or provided any mitigation, restricting access to the vulnerable endpoint or implementing web application firewall (WAF) rules to block malicious SQL injection attempts may help reduce risk temporarily. [2]
How can this vulnerability impact me? :
The vulnerability can allow an attacker to execute unauthorized SQL commands on the database, potentially leading to data leakage, data modification, or denial of service. Since it can be exploited remotely without authentication, it poses a significant security risk.