Bogo · Security record

Is Bogo safe?

No known vulnerability affects the current version (3.9.3). 1 issue was found in earlier versions and fixed, the latest disclosed on Jun 18, 2026.

Checked 4 days ago against the WPVulnerability database, for version 3.9.3.

How it’s looked after

Last release: Aug 18, 2026 (2 months ago)
Releases in the last year: 3
Tested up to: WordPress 7.1.4
Support resolved: 0 of 2 threads in two months
Active installs: 10K+

1 known vulnerability

1 medium

None affects the current version.

Every known vulnerability in Bogo

Newest first, with any that affect the current version at the top.

medium
Missing Authorization to Authenticated (Subscriber+) Sensitive Information Exposure via REST API
Fixed in 3.9.2 · CVE-2026-9013 · Jun 18, 2026 · Wordfence

Questions about Bogo’s security

Is Bogo safe to use?

No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Bogo updated: most attacks target sites that haven’t updated.

Does Bogo have known security vulnerabilities?

None that affect the current version. WPVulnerability’s database lists 1 older issue, fixed in earlier versions, so keep Bogo up to date.

Is Bogo still maintained?

Yes. Its last release was 2 months ago. Its authors resolved 0 of the 2 support threads opened in the last two months.

Is Bogo compatible with the latest WordPress?

Yes. It’s tested up to WordPress 7.1.4, the current version.

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 free

Vulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.