Is WebberZone Top 10 safe?

No known vulnerability affects the current version (4.6.2). 20 issues were found in earlier versions and fixed, the latest disclosed on May 7, 2025.

Checked 3 days ago against the WPVulnerability database, for version 4.6.2.

How it’s looked after

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

20 known vulnerabilities

7 medium
13 not rated

None affects the current version.

Disclosed each year

20151
20162
20172
20202
20221
20237
20252

Every known vulnerability in WebberZone Top 10

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

medium
Authenticated (Contributor+) Stored Cross-Site Scripting via 'other_attributes' Block Attribute
Fixed in 4.5.3 · CVE-2026-110290 · May 7, 2025 · Wordfence
medium
Authenticated (Contributor+) Stored Cross-Site Scripting
Fixed in 4.1.1 · CVE-2025-47509 · May 7, 2025 · Wordfence
medium
Cross-Site Request Forgery via edit_count_ajax
Fixed in 3.3.3 · CVE-2023-47238 · Nov 3, 2023 · Wordfence
CVE split into individual CVE IDs for each software record.
Fixed in 2.9.5 · CVE-2021-4342 · Jun 7, 2023 · CVE
WordPress Top 10 Plugin <= 3.2.4 is vulnerable to Broken Access Control
Fixed in 3.2.5 · Feb 24, 2023 · Patchstack
medium
Authenticated(Admin+) Stored Cross-Site Scripting
Fixed in 3.2.5 · CVE-2023-26008 · Feb 22, 2023 · Wordfence
Missing Authorization on tptn_chart_data
Fixed in 3.2.5 · Feb 22, 2023 · Wordfence
Cross-Site Request Forgery via tptn_ajax_clearcache
Fixed in 3.2.4 · Feb 20, 2023 · Wordfence
medium
Missing Authorization on tptn_ajax_clearcache
Fixed in 3.2.4 · CVE-2023-25993 · Feb 20, 2023 · Wordfence
medium
Authenticated (Contributor+) Stored Cross-Site Scripting via Blocks
Fixed in 3.2.3 · CVE-2022-4570 · Dec 29, 2022 · Wordfence
medium
Cross-Site Request Forgery Bypass
Fixed in 2.9.5 · CVE-2020-36761 · Sep 16, 2020 · Wordfence
Cross-Site Request Forgery (CSRF) vulnerability
Fixed in 2.9.5 · Sep 16, 2020 · Patchstack
Authenticated SQL Injection (SQLi) vulnerability
Fixed in 2.4.4 · Dec 20, 2017 · Patchstack
SQL Injection
Fixed in 2.4.4 · Dec 13, 2017 · Wordfence
Cross-Site Scripting
Fixed in 2.3.1 · Jul 15, 2016 · Wordfence
Cross Site Scripting
Fixed in 2.3.1 · Jul 14, 2016 · Patchstack
Cross Site Request Forgery
Fixed in 1.9.3 · May 15, 2015 · Patchstack
Cross-Site Scripting (XSS)
Fixed in 2.3.1 · WPScan
Authenticated SQL Injection
Fixed in 2.4.4 · WPScan
404 Page Not Found
Fixed in 2.9.5 · Wordfence

Questions about WebberZone Top 10’s security

Is WebberZone Top 10 safe to use?

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

Does WebberZone Top 10 have known security vulnerabilities?

None that affect the current version. WPVulnerability’s database lists 20 older issues, fixed in earlier versions, so keep WebberZone Top 10 up to date.

Is WebberZone Top 10 still maintained?

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

Is WebberZone Top 10 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.