php-thinkphp-audit

Map ThinkPHP security weaknesses to risk categories via static analysis.

386|38|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/0xShe/PHP-Code-Audit-Skill --skill php-thinkphp-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: php-thinkphp-audit
Source: https://github.com/0xShe/PHP-Code-Audit-Skill/tree/main/php-thinkphp-audit
Command: npx skills add https://github.com/0xShe/PHP-Code-Audit-Skill --skill php-thinkphp-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ThinkPHP 项目在安全审计中缺乏系统化的静态分析工具。本 Skill 针对 ThinkPHP 框架的常见安全机制(鉴权、CSRF、模板转义、Mass Assignment、调试与配置暴露等)进行白盒静态审计,并将结果映射到通用漏洞类型体系。

Core Features & Use Cases

  • 将 ThinkPHP 项目源码作为输入,识别并标注认证/权限控制薄弱点、CSRF 保护缺失、模板输出风险、Mass Assignment 漏洞入口、调试与配置暴露等问题。
  • 将分析结果映射到 AUTH / CSRF / TPL / LOGIC / CFG 等通用风险类别,便于跨框架对比与修复优先级排序。
  • 产出可追溯的证据链和可操作的修复建议,帮助开发者在上线前进行回归验证。

Quick Start

ThinkPHP 项目根目录作为输入,运行审计以输出框架审计报告.

Frequently Asked Questions about php-thinkphp-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I perform a static security audit on a ThinkPHP PHP project?

To perform a ThinkPHP static security audit, input the ThinkPHP project root directory to identify authentication, CSRF, mass assignment, and template escaping weaknesses, receiving structured audit outputs mapped to risk categories.

What security vulnerabilities are commonly found in ThinkPHP framework applications?

Common ThinkPHP security vulnerabilities include weak authentication, missing CSRF protection, template output risks, mass assignment entry points, and debug or config exposure, which static analysis can map to risk categories.

Does this static analysis tool support white-box audits for ThinkPHP template escaping and mass assignment?

Yes, it supports white-box audits for ThinkPHP template escaping and mass assignment by analyzing source code to identify vulnerability entry points and producing traceable evidence chains mapped to TPL and LOGIC risk categories.

Can I use this to map ThinkPHP security findings to general vulnerability categories for cross-framework comparison?

Yes, you can map ThinkPHP security findings to general vulnerability categories like AUTH, CSRF, TPL, LOGIC, and CFG, enabling cross-framework comparison and structured remediation prioritization based on traceable evidence.

What are the limitations of static analysis for ThinkPHP debugging and config exposure risks?

Static analysis for ThinkPHP debugging and config exposure identifies code-level weaknesses by tracing framework evidence, but it may not detect runtime environment misconfigurations or dynamically loaded vulnerabilities outside the source code scope.