Custom Body Class · Security record
Is Custom Body Class safe?
No known vulnerability affects the current version (0.7.5). 4 issues were found in earlier versions and fixed, the latest disclosed on Dec 12, 2019.
Checked 4 days ago against the WPVulnerability database, for version 0.7.5.
How it’s looked after
- Last release
- Jul 27, 2025 (1 year ago)
- Releases in the last year
- 0
- Tested up to
- WordPress 6.8.12 (current: 7.1)
- Support resolved
- 0 of 1 threads in two months
- Active installs
- 10K+
4 known vulnerabilities
- 1 high
- 1 medium
- 2 not rated
None affects the current version.
Every known vulnerability in Custom Body Class
Newest first, with any that affect the current version at the top.
Fixed in 0.7.0 · CVE-2019-6030 · Dec 12, 2019 · Wordfence
- medium
Cross-Site Scripting
Fixed in 0.7.0 · CVE-2019-6029 · Dec 12, 2019 · Wordfence
Fixed in 0.7.1 · Jul 15, 2019 · Patchstack
Fixed in 0.7.1 · WPScan
Questions about Custom Body Class’s security
Is Custom Body Class safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Custom Body Class updated: most attacks target sites that haven’t updated.
Does Custom Body Class have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 4 older issues, fixed in earlier versions, so keep Custom Body Class up to date.
Is Custom Body Class still maintained?
Its last release was 1 year ago, so it may no longer be actively maintained. Its authors resolved 0 of the 1 support threads opened in the last two months.
Is Custom Body Class compatible with the latest WordPress?
Custom Body Class’s readme says it’s tested up to WordPress 6.8.12, 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.