Antispam Bee
Antispam Bee has one disclosed vulnerability in the WordSec catalog, all reported in 2023; it is fixed as of September 2026. Their average CVSS score is 5.3, and the most serious one scores 5.3 out of 10.
The most common weakness is Reliance On Untrusted Inputs In A Security Decision, behind 1 of the records (100%).
The one issue recorded for Antispam Bee has a vendor fix available, so running the current release closes it.
All of these findings were reported by Kévin Mosbahi (Mika). Antispam Bee is installed on roughly 700,000 WordPress sites, so each unpatched flaw has a wide blast radius. The current release is tested up to WordPress 7.1.
CVE-2023-41134Antispam Bee <= 2.11.3 - IP Address Spoofing via get_client_ip
Read the full analysisVulnerability Records

Antispam Bee
Author
pluginkollektiv
Say Goodbye to comment spam on your WordPress blog or website. Antispam Bee blocks spam comments and trackbacks effectively, without captchas and without sending personal information to third party services. It is free of charge, ad-free and 100% GDPR compliant. Feature/Settings Overview Trust approved commenters. Trust commenters with a Gravatar. Consider the comment time. Allow comments only in a certain language. Block or allow commenters from certain countries. Treat BBCode links as spam. Use regular expressions. Search local spam database for commenters previously marked as spammers. Notify admins by e-mail about incoming spam. Delete existing spam after n days. Limit approval to comments/pings (will delete other comment types). Select spam indicators to send comments to deletion directly. Optionally exclude trackbacks and pingbacks from spam detection. Optionally spam-check comment forms on archive pages. Display spam statistics on the dashboard, including daily updates of spam detection rate and a total of blocked spam comments. Support Community support via the support forums on wordpress.org Read the documentation We don’t handle support via e-mail, Twitter, GitHub issues etc. Contribute Active development of this plugin is handled on GitHub. Pull requests for documented bugs are highly appreciated. If you think you’ve found a bug (e.g. you’re experiencing unexpected behavior), please post at the support forums first. If you want to help us translate this plugin you can do so on WordPress Translate. Credits Author: Sergej Müller Maintainers: pluginkollektiv
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C