BlossomThemes Email Newsletter · Security record
Is BlossomThemes Email Newsletter safe?
No known vulnerability affects the current version (2.2.11). 2 issues were found in earlier versions and fixed, the latest disclosed on Jun 20, 2024.
Checked 6 days ago against the WPVulnerability database, for version 2.2.11.
How it’s looked after
- Last release
- Apr 6, 2026 (7 months ago)
- Releases in the last year
- 1
- Tested up to
- WordPress 6.7.11 (current: 7.1)
- Active installs
- 10K+
2 known vulnerabilities
- 1 critical
- 1 medium
None affects the current version.
Disclosed each year
- 20231
- 20241
Every known vulnerability in BlossomThemes Email Newsletter
Newest first, with any that affect the current version at the top.
Fixed in 2.2.7 · CVE-2024-37098 · Jun 20, 2024 · Wordfence
- medium
Missing Authorization
Fixed in 2.2.5 · CVE-2023-47849 · Nov 20, 2023 · Wordfence
Questions about BlossomThemes Email Newsletter’s security
Is BlossomThemes Email Newsletter safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep BlossomThemes Email Newsletter updated: most attacks target sites that haven’t updated.
Does BlossomThemes Email Newsletter have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 2 older issues, fixed in earlier versions, so keep BlossomThemes Email Newsletter up to date.
Is BlossomThemes Email Newsletter still maintained?
Its last release was 7 months ago. No support threads were opened in the last two months.
Is BlossomThemes Email Newsletter compatible with the latest WordPress?
BlossomThemes Email Newsletter’s readme says it’s tested up to WordPress 6.7.11, 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.