Brisk Vulnerabilities
The Brisk WordPress theme has 1 known security vulnerability. The most recent was disclosed on September 29, 2012. Check whether your site runs an affected version below.
View Brisk on WordPress.orgSummary
Latest vulnerability disclosed on September 29, 2012.
Recommendation
WPSentry recommends keeping it updated
Brisk's known issues are medium severity and are generally fixed in newer releases. Keep this theme fully up to date and scan your site regularly.
Is your site affected?
Run a free external scan to detect Brisk and 35+ other WordPress security checks — no login or plugin required.
Known Brisk vulnerabilities
- medium
Brisk (Unknown Versions) - Cross-Site Scripting
Affected versions: <=*Disclosed September 29, 2012
How to stay protected
Update promptly
Keep Brisk on its latest release — most vulnerabilities are fixed in newer versions.
Scan regularly
Run an external scan after every update to catch outdated or vulnerable software early.
Monitor continuously
Enable monitoring to get alerted the moment a new issue affects your stack.