For Typecho, PHP2Shell remediation requires patching the PHP runtime. The application version helps identify compatibility blockers; it cannot establish exploitability or prove that either CVE is fixed.

Typecho - PHP compatibility for the PHP2Shell fix

Release sampleDeclared PHP requirementDeclared patch candidatesOriginal source
v1.3.0>=7.4.0raw.githubusercontent.com ↗
v1.2.1>=7.2.0raw.githubusercontent.com ↗

Candidates match only this declaration against the first PHP2Shell fixes on supported branches. They do not establish tested compatibility, vendor support or a complete dependency match. PHP compatibility for the PHP2Shell fix ↗

Identify the PHP2Shell repair scope

Files and package identity

  • var/Typecho/Common.php
  • usr/plugins/
  • usr/themes/

Typecho - Remove blockers to patch PHP2Shell

Typecho’s README provides a minimum for each sampled tag, not an assurance for every theme or plugin. Inspect plugin hooks, theme functions, database adapters and custom routing before changing PHP. Back up the database and usr/ together. After the official update process, compare permalinks, comments, Markdown rendering and uploaded media with the original site.

Dependencies and custom code to review

  • Typecho
  • functions.php
  • Plugin.php
  • Typecho\Db
  • Markdown
  • usr/uploads/
  • routingTable
Official upgrade documentation ↗

Check site functions after the PHP2Shell fix

Inventory before fixing PHP2Shell

Use an authorized working copy.

Command example
php -v
php --ini
php -m

Typecho - PHP2Shell patch verification

Verify both CVE fixes in the PHP actually serving this site. Replace or restart old Web workers, queue workers and replicas. A working homepage or a newer CLI binary is insufficient evidence.

3. Restart and verify every instance ↗

Official upgrade documentation

TypechoOriginal source ↗PHP security teamOriginal source ↗CVE-2026-109618Original source ↗CVE-2026-109619Original source ↗PHP2Shell repair - solve PHP upgrade errors↗

Related applications

← Back to application guides