Is WP BrowserUpdate safe?

No known vulnerability affects the current version (6.0.1). 2 issues were found in earlier versions and fixed, the latest disclosed on Apr 24, 2023.

Checked 2 days ago against the WPVulnerability database, for version 6.0.1.

How it’s looked after

Last release: Aug 13, 2026 (2 months ago)
Releases in the last year: 3
Tested up to: WordPress 7.1.4
Active installs: 1K+

2 known vulnerabilities

2 medium

None affects the current version.

Every known vulnerability in WP BrowserUpdate

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

medium
Authenticated (Admin+) Stored Cross-Site Scripting
Fixed in 4.6 · CVE-2023-28690 · Apr 24, 2023 · Wordfence
medium
Cross-Site Request Forgery via wpbu_administration
Fixed in 4.5 · CVE-2023-31078 · Apr 24, 2023 · Wordfence

Questions about WP BrowserUpdate’s security

Is WP BrowserUpdate safe to use?

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

Does WP BrowserUpdate have known security vulnerabilities?

None that affect the current version. WPVulnerability’s database lists 2 older issues, fixed in earlier versions, so keep WP BrowserUpdate up to date.

Is WP BrowserUpdate still maintained?

Yes. Its last release was 2 months ago. No support threads were opened in the last two months.

Is WP BrowserUpdate 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.