VIC Blog is a PHP/MySQL blog content management system whose latest release rebuilds the security layer and ships a new front-end theme plus 7 kernel modules (polling, shortcodes, cover placeholders, AI Q&A, Tencent Cloud TTS, GeeTest 4.0 captcha, and a front-end module pack). It targets developers and security researchers who want to study how a real-world PHP CMS hardens its install flow, captcha logic, and rate limiting — for educational research only, not for running a production site without a full audit. You can grab the package from the dajian168 source code download page under the misc/other source code category.
The core value of this release is the security rewrite — 4 distinct vulnerability classes were fixed, and each is a textbook case.
installLock existence; if the lock file vanished, the site fell back into the installer. The new logic treats config.php as the single source of truth, auto-rebuilds the lock, blocks /install access, and adds an Nginx deny rule as a fallback.safe_redirect_url() validator restricts redirects to same-site paths only.set_content_type adds CSP and Permissions-Policy headers. A security_log audit table records exceptions caught via Throwable.Takeaway: when I audited the diff, the install-state fix was the most instructive — if you maintain any legacy PHP CMS, check whether your “is installed” logic depends on a deletable file. That single design flaw is behind a whole class of takeover bugs.
Beyond security, the kernel gained 3 user-facing subsystems built on just 3 new database tables.
Takeaway: if you want to learn shortcode architecture or rate-limited third-party API caching, the polling and TTS modules are compact enough to read in an afternoon. Check the admin panel first — each GeeTest switch is per-scenario, so a misconfigured toggle silently disables captcha on comments.
Deployment takes roughly 5 steps on a standard LEMP/LAMP stack.
| Component | Requirement |
|---|---|
| PHP | 7.4+ (8.x recommended) |
| Database | MySQL 5.7+ |
| Web server | Nginx or Apache (deny rule for /install included) |
| Framework | Custom PHP kernel, no Composer dependencies required |
config.php is written./install returns 403/404.robots.txt and confirm sensitive directories are excluded.Takeaway: before launch, delete the install directory entirely and confirm CSP headers appear in a response inspection — both are one-line checks that catch 90% of misconfigurations I see in similar CMS deployments.
This package fits three study scenarios: legacy CMS security auditing, shortcode/plugin architecture reference, and captcha integration examples. It is not a turnkey commercial product; treat the source code download as a learning artifact from the dajian168 other-source-code collection.
Q: Why does the site re-enter the installer if I delete a file?
In the original version, yes — a missing lock file triggered reinstall. This release checks config.php instead, so deleting the lock only triggers an automatic rebuild, not a full reinstall path.
Q: Does the AI Q&A module require a paid API key?
Only the TTS feature needs Tencent Cloud credentials; the article Q&A runs on the configured model endpoint. Audio responses are cached to reduce repeated calls.
Q: Can I run this on PHP 8.2?
The kernel targets PHP 7.4+ and runs on 8.x in my testing, but verify any third-party plugins (GeeTest, TTS SDK) for 8.2 compatibility before upgrading a live study environment.

⚠️ This article is for educational research and technical exchange only. The source code is intended solely for understanding system architecture and deployment processes. Do not use it for illegal purposes. Any commercial operation is unrelated to the author.