State of WordPress security – insights from 2022
summary
Data shows 4,528 security vulnerabilities in 2022 with 99.7% in plugins and themes and only 26 in WordPress core, driven largely by two widely used frameworks that create a supply chain ripple. A Patch Alliance program receives 1,160 reports, validates 748, escalates 148, and finds that 26% of critical bugs remain unpatched while roughly 10% of escalated plugins are closed—so rely on virtual patching, EOL notices, managed hosting that monitors plugins, and public vulnerability disclosure programs.
AI-written summary · about
chapters (28)
- 0:00Introduction and speaker background
- 1:52WordPress security trends 2020-2022
- 3:40Core vs plugins security maturity
- 5:45Software supply chain challenges
- 7:08Patch Alliance program insights
- 9:17Abandoned plugins security risks
- 10:00Critical vulnerabilities patch delays
- 11:24WordPress admin panel security alerts
- 12:26End-of-life plugin communication
- 13:53Handling security reports rejection
- 14:55Security researchers as contributors
- 16:19Choosing minimal plugin stacks
- 17:23Virtual patching benefits
- 18:06Hosting providers security role
- 18:482023 security expectations
- 20:14Government regulation of open source
- 21:59Key takeaways and future outlook
- 23:03Q&A session introduction
- 23:23Plugin developer security practices
- 25:29Plugin closure and patching policies
- 26:33JavaScript dependency risks
- 27:56Vulnerability reporting scope
- 30:04DevSecOps tools for developers
- 31:29Community pressure on developers
- 33:38Hiding vulnerabilities in changelogs
- 36:05Pre-upload plugin security checks
- 38:12Other major vulnerability categories
- 39:39Q&A wrap-up and closing
