Belaka · Security record
Is Belaka safe?
No known vulnerability affects the current version (2.0.2). 1 issue was found in earlier versions and fixed, the latest disclosed on Aug 10, 2026.
Checked 2 days ago against the WPVulnerability database, for version 2.0.2.
How it’s looked after
- Last release
- Nov 2, 2026 (6 days ago)
- Releases in the last year
- 3
- Tested up to
- WordPress 7.1.4
- Support resolved
- 0 of 1 threads in two months
- Active installs
- 1K+
1 known vulnerability
- 1 not rated
None affects the current version.
Every known vulnerability in Belaka
Newest first, with any that affect the current version at the top.
Fixed in 2.0.1 · CVE-2026-18960 · Aug 10, 2026 · Wordfence
Questions about Belaka’s security
Is Belaka safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Belaka updated: most attacks target sites that haven’t updated.
Does Belaka have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 1 older issue, fixed in earlier versions, so keep Belaka up to date.
Is Belaka still maintained?
Yes. Its last release was 6 days ago. Its authors resolved 0 of the 1 support threads opened in the last two months.
Is Belaka 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 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.