CVE-2025-50706
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 · uneditedAn issue in thinkphp v.5.1 allows a remote attacker to execute arbitrary code via the routecheck function
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 · moderate confidenceThinkPHP v5.1 contains a remote code execution vulnerability in the routecheck function, allowing unauthenticated remote attackers to execute arbitrary code on the affected server via specially crafted requests.
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.1.0CVSS 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 ThinkPHP installation versionCheck the version.php file in the ThinkPHP core directory, or view the header of any ThinkPHP source file that contains version information. Common paths include /thinkphp/base.php or /thinkphp/convention.php.Affected if The installed version matches 5.1.0 or falls within the ThinkPHP v5.1 branch.
-
Locate the routecheck functionalitySearch the ThinkPHP source code for the routecheck function or RouteCheck class. This is typically found in the routing or request handling module.Affected if The routecheck function exists and is accessible in the installed version.
-
Verify routing accessibilityExamine the application routing configuration in route/ directory and the URL routing rules defined in the application. Check if route matching is enabled in the application configuration.Affected if Route matching is enabled and accessible without authentication.
-
Check for unauthenticated route accessReview the application configuration file (config.php or app.php) for route authentication settings. Look for any middleware or filters that may protect the routecheck mechanism.Affected if No authentication or authorization is required to access routecheck functionality.
-
Test route pattern matching behaviorIf safe testing is authorized, send a crafted request that would trigger the routecheck function with a malicious route pattern to observe if the vulnerability is exploitable.Affected if The application processes route patterns through routecheck without proper sanitization, allowing arbitrary code execution.
A user is affected if they are running ThinkPHP v5.1 with the routecheck function accessible and without authentication protection on route processing.
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.
From vendor dataUpgrade to a patched version of ThinkPHP (v5.1.42+ or latest v5.1 LTS) or apply official security patches; if immediate patching is not possible, restrict access to vulnerable endpoints at the network level.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-50706 — 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-2025-50706 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