WPGlobus for WPBakery Visual Composer · Security record
Is WPGlobus for WPBakery Visual Composer safe?
No known vulnerabilities are on record for WPGlobus for WPBakery Visual Composer.
Checked 5 days ago against the WPVulnerability database, for version 2.2.1.
How it’s looked after
- Last release
- Nov 18, 2022 (3 years ago)
- Releases in the last year
- 0
- Tested up to
- WordPress 6.1.16 (current: 7.1)
- Active installs
- 2K+
Known vulnerabilities
None on record for WPGlobus for WPBakery Visual Composer.
Questions about WPGlobus for WPBakery Visual Composer’s security
Is WPGlobus for WPBakery Visual Composer safe to use?
No known vulnerabilities are on record for WPGlobus for WPBakery Visual Composer. That isn’t a guarantee, so keep it updated like any plugin.
Does WPGlobus for WPBakery Visual Composer have known security vulnerabilities?
No. WPVulnerability’s database lists no known vulnerabilities for WPGlobus for WPBakery Visual Composer.
Is WPGlobus for WPBakery Visual Composer still maintained?
Its last release was 3 years ago, so it may no longer be actively maintained. No support threads were opened in the last two months.
Is WPGlobus for WPBakery Visual Composer compatible with the latest WordPress?
WPGlobus for WPBakery Visual Composer’s readme says it’s tested up to WordPress 6.1.16, while the current version is 7.1. That doesn’t mean it breaks, but its author hasn’t confirmed it works with the latest releases.
Hear about the next one first
Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.
Start freeVulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.