Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
HIGH severity

GHSA-75jp-87w2-c6x2

HIGH

GHSA-75jp-87w2-c6x2 is a high-severity (CVSS 8.8) remote code execution vulnerability in topthink/framework. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-75jp-87w2-c6x2 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

ThinkPHP Remote Code Execution (RCE) vulnerability

Also known asCVE-2021-44892
Published
Feb 11, 2022
Updated
Apr 24, 2024
Affected
1 pkg
Patched
None yet
Exploits
1 known
Exploitation data as of Apr 24, 2024 · OSV.dev, NVD, FIRST.org (EPSS)

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

A Remote Code Execution (RCE) vulnerability exists in ThinkPHP 3.x.x via value[_filename] in index.php, which could let a malicious user obtain server control privileges.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
🐘Packagisttopthink/frameworkall versionsNo fix
Exploits & PoCs
1

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

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for topthink/framework. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Remediation status

    No patched version of topthink/framework has shipped for GHSA-75jp-87w2-c6x2 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-75jp-87w2-c6x2 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-75jp-87w2-c6x2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A Remote Code Execution (RCE) vulnerability exists in ThinkPHP 3.x.x via value[_filename] in index.php, which could let a malicious user obtain server control privileges.
O3 Security · Impact-Aware SCA

Is GHSA-75jp-87w2-c6x2 in your dependencies?

O3 detects GHSA-75jp-87w2-c6x2 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-75jp-87w2-c6x2: ThinkPHP Remote… | O3 Security