dbcve.org
InjectionWeakness · CWE-74

CVE-2025-15142

HIGH · 7.3 CVSS v3.1 Published 2025-12-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in phpok3w's show.php file via the ID parameter allows remote attackers to inject malicious SQL queries. The exploit is publicly available and no official patch exists as the project has not responded to the reported issue.

MitigationImplement input validation and use parameterized queries/prepared statements for all database operations involving user-supplied input. Since the upstream project hasn't responded, consider manual patching or implementing a Web Application Firewall as a temporary measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate phpok3w installation
    Search the web root directory for files or directories named 'phpok3w' or 'phpok'. Common paths include /var/www/html/, /www/, or C:\inetpub\wwwroot\. Look for the main index.php or admin.php files typical of this CMS.
    Affected if The phpok3w software is present on the server.
  2. Find the vulnerable show.php file
    Navigate to the phpok3w installation directory and locate the show.php file. This is typically found in the root or a front controller directory of the application.
    Affected if The show.php file exists in the phpok3w installation.
  3. Inspect the ID parameter handling in show.php
    Open show.php in a text editor or use 'grep -n "ID" show.php' or 'Select-String -Path show.php -Pattern "ID"' to locate where the ID parameter is processed. Look for code that directly uses $_GET['ID'], $_POST['ID'], or similar superglobals in SQL queries without sanitization.
    Affected if The ID parameter is directly used in database queries without prepared statements or parameterization.
  4. Check for SQL injection sinks
    Search for common database query functions in show.php such as 'query(', 'execute(', 'mysqli_query(', 'PDO::query(', or similar. Verify if user-supplied ID input flows into these functions unsafely.
    Affected if User input from the ID parameter flows into SQL queries without escaping or parameter binding.
  5. Identify the installed version
    Check version files such as version.php, CHANGELOG.md, README.md, or a config file within the phpok3w directory. Also check the footer of the admin panel or any meta tags in the HTML source.
    Affected if A specific version cannot be determined from available files, assume all versions are potentially affected.

If phpok3w is installed and the show.php file handles the ID parameter without prepared statements or input sanitization, the environment is vulnerable to CVE-2025-15142.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement input validation and use parameterized queries/prepared statements for all database operations involving user-supplied input. Since the upstream project hasn't responded, consider manual patching or implementing a Web Application Firewall as a temporary measure.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-15142 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-15142 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data