CVE-2018-25270
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 · uneditedThinkPHP 5.0.23 contains a remote code execution vulnerability that allows unauthenticated attackers to execute arbitrary PHP code by invoking functions through the routing parameter. Attackers can craft requests to the index.php endpoint with malicious function parameters to execute system commands with application privileges.
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 confidenceThinkPHP 5.0.23 contains an unauthenticated remote code execution vulnerability where attackers can invoke arbitrary functions through the routing parameter in index.php, allowing execution of system commands with application-level privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 5.0.0, < 5.0.23= 5.1.31CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed ThinkPHP versionCheck the ThinkPHP version file or framework core files for the version number. This is typically found in the ThinkPHP library files or a version.php file within the framework.Affected if The installed version is 5.0.0 through 5.0.22 (inclusive), or exactly version 5.1.31.
-
Verify the routing mechanism is accessibleConfirm that the application index.php is accessible and processes route parameters. This is the entry point where the vulnerability can be triggered.Affected if The index.php routing parameter processing is exposed and accessible without authentication.
-
Check if the application handles user-controlled route parametersReview the application configuration and routing logic in index.php to determine if route parameters passed via URL are processed and used to invoke functions.Affected if The application accepts and processes arbitrary function names through route parameters without sanitization.
A system is affected if it runs ThinkPHP version 5.0.0 through 5.0.22, or exactly version 5.1.31, and has its routing parameter mechanism in index.php exposed and accessible without authentication.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scoped5.0.23
Upgrade ThinkPHP to version 5.0.24 or later which contains the patch; alternatively, deploy a WAF rule to block requests with suspicious function names in route parameters until the upgrade can be completed.
ThinkPHP 5.0.23+ or 5.1.32+
- 1. Identify the exact ThinkPHP version currently installed by checking the thinkphp/base.php or composer.json file
- 2. For ThinkPHP 5.0.x branch: Upgrade to version 5.0.23 or later by running 'composer require topthink/framework ^5.0.23'
- 3. For ThinkPHP 5.1.x branch: Upgrade to version 5.1.32 or later by running 'composer require topthink/framework ^5.1.32'
- 4. Clear all cached files in the runtime/ directory after upgrade
- 5. Test application functionality to ensure the upgrade does not break existing features
- 6. Verify the vulnerability is patched by attempting the documented attack vector (e.g., requests to index.php with malicious _method parameter)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-25270 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-25270 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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