Highlighting Code Block · Security record
Is Highlighting Code Block safe?
No known vulnerability affects the current version (2.2.1). 1 issue was found in earlier versions and fixed, the latest disclosed on Jul 9, 2026.
Checked 4 days ago against the WPVulnerability database, for version 2.2.1.
How it’s looked after
- Last release
- Jul 1, 2026 (4 months ago)
- Releases in the last year
- 5
- Tested up to
- WordPress 7.0.8
- Support resolved
- 0 of 1 threads in two months
- Active installs
- 10K+
1 known vulnerability
- 1 medium
None affects the current version.
Every known vulnerability in Highlighting Code Block
Newest first, with any that affect the current version at the top.
Fixed in 2.2.1 · CVE-2026-12108 · Jul 9, 2026 · Wordfence
Questions about Highlighting Code Block’s security
Is Highlighting Code Block safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Highlighting Code Block updated: most attacks target sites that haven’t updated.
Does Highlighting Code Block have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 1 older issue, fixed in earlier versions, so keep Highlighting Code Block up to date.
Is Highlighting Code Block still maintained?
Yes. Its last release was 4 months ago. Its authors resolved 0 of the 1 support threads opened in the last two months.
Is Highlighting Code Block compatible with the latest WordPress?
It’s tested up to WordPress 7.0.8, one version behind the current 7.1. Authors often update this line a few weeks after a release.
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.