How severe is CVE-2018-16385?

CVE-2018-16385 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2018-16385?

CVE-2018-16385 affects the following packages: topthink/framework (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2018-16385?

Update topthink/framework to 5.1.23 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-16385 is resolved across your whole dependency graph.

How do I detect CVE-2018-16385 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for topthink/framework, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2018-16385 if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is CVE-2018-16385 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2018-16385, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2018-16385?

CVE-2018-16385 has an EPSS (Exploit Prediction Scoring System) score of 2.2%, placing it in the 82th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2018-16385?

CVE-2018-16385 is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2018-16385 published, and has it been updated?

CVE-2018-16385 was published on September 3, 2018 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

CRITICAL severity

CVE-2018-16385 — framework

CRITICAL

CVE-2018-16385 is a critical-severity (CVSS 9.8) SQL Injection vulnerability in topthink/framework. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for topthink/framework — see the affected versions and patch details below.

ThinkPHP SQL Injection vulnerability

Also known asGHSA-vcm7-88jx-3r39

Published

Sep 3, 2018

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs82th percentile — riskier than 82% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐘topthink/framework

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

ThinkPHP before 5.1.23 allows SQL Injection via the public/index/index/test/index query string.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`topthink/framework`	all versions	5.1.23`composer require topthink/framework:^5.1.23`

Affected Products

1 product · 1 configurations

Application

thinkphpthinkphp

< 5.1.23

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

ThinkPHP before 5.1.23 allows SQL Injection via the public/index/index/t…

github.comNVDOct 2018

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for topthink/framework, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update topthink/framework to 5.1.23 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-16385 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Frequently Asked Questions

ThinkPHP before 5.1.23 allows SQL Injection via the public/index/index/test/index query string.

O3 Security · Impact-Aware SCA

Is CVE-2018-16385 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

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

CWE Classification

CWE-89SQL Injection

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

OpenSSF Scorecard

Package health score

framework

2.9/10

Maintained0/10

Code-Review0/10

Branch-ProtectionN/A

Assessed Oct 26, 2026

Timeline

Disclosed

Sep 3, 2018

First exploit

Oct 31, 2018

Last updated

Oct 24, 2026

Identifiers

CVE-2018-16385

GHSA-vcm7-88jx-3r39

References

Advisoryexchange.xforce.ibmcloud.com Advisorynvd.nist.gov · CVE 2018 16385 Packagegithub.com · framework Evidencegithub.com

Related vulnerabilities

This CVE is critical severity; 6 of 8 other CVEs affecting topthink/framework are rated as high or higher (top: critical).

CVE-2025-50706CVE-2024-44902CVE-2024-34467CVE-2022-47945CVE-2022-44289CVE-2022-38352CVE-2022-33107CVE-2018-17566

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2018-16385 — framework

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2018-16385 in your dependencies?