Application Security For WordPress Developers
summary
Covers concrete WordPress failures: leaving a WP‑CLI DB dump in the web root exposes all user data; XML‑RPC and PHP unserialize on plugin inputs let attackers run code and take over servers; form or translation strings allow XSS to steal cookies or inject fake login forms; forged requests exploit missing nonces and permissions as CSRF to change data. Recommends using WP APIs, permission checks and nonces, run PHP_CodeSniffer with WordPress Coding Standards, use fail2ban and a firewall (Cloudflare/managed) to block automated exploit bots.
AI-written summary · about
chapters (14)
- 0:00Introduction to WordPress security
- 1:08OWASP top vulnerabilities overview
- 4:19Sensitive data exposure risks
- 7:29Security misconfiguration examples
- 9:18Injection vulnerabilities explained
- 12:04Cross-site scripting threats
- 15:35Insecure direct object references
- 17:23Missing function access control
- 19:08Cross-site request forgery risks
- 25:39Protecting against automated attacks
- 27:30Authentication security best practices
- 28:11Recommended security plugins
- 30:51Developer resources for security
- 33:32Q&A on security practices
