Stop Spammers Classic at a glance
- 10 publicly disclosed vulnerabilities, 2 of them rated High or Critical. The most recent was disclosed on Nov 6, 2026.
- Ranked #1115 by popularity on WordPress.org (20,000+ active installs).
- The latest version is 2026.7 (released Nov 4, 2026). The most recent security fix shipped in 2026.7.
- Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
- The first thing to do: update to the latest version and turn on automatic updates.
Check your Stop Spammers Classic version
Enter the Stop Spammers Classic version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.
Your version number is compared on this page only. It is not sent anywhere.
Get an email when a new vulnerability is disclosed
We'll tell you when a new vulnerability is disclosed in “Stop Spammers Classic”, with the version that fixes it. Free, email address only, stop any time.
We use your email address only for these alerts. Privacy policy
Want every plugin and theme on your site checked daily?
With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.
How to check whether your site is affected
- 1
Find your version
In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Stop Spammers Classic”.
- 2
Compare it with the list below
If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.
- 3
Update
Click “Update now” to move to the latest version (2026.7). Taking a backup first is a good idea.
- 4
Turn on automatic updates
On the same screen, click “Enable auto-updates” so future fixes are installed automatically.
Known Stop Spammers Classic vulnerabilities
Stop Spammers Classic <= 2026.6 - Unauthenticated Stored Cross-Site Scripting via 'author' Parameter
Cross-site scripting (XSS) · CVE-2026-120477
Affected versions: ≤ 2026.6
Fixed in: 2026.7
Severity: Medium 4.7 · Disclosed Nov 6, 2026
Stop Spammers Classic <= 2026.3 - Unauthenticated Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2026-48876
Affected versions: ≤ 2026.3
Fixed in: 2026.4
Severity: High 7.2 · Disclosed Jun 1, 2026
Stop Spammers Classic <= 2026.1 - Cross-Site Request Forgery via Email Allowlist
Cross-site request forgery (CSRF) · CVE-2025-14795
Affected versions: ≤ 2026.1
Fixed in: 2026.2
Severity: Medium 4.3 · Disclosed Jan 27, 2026
Anti-Spam: Spam Protection | Block Spam Users, Comments, Forms <= 2024.7 - Cross-Site Request Forgery to Multiple Administrative Actions
Cross-site request forgery (CSRF) · CVE-2025-2935
Affected versions: ≤ 2024.7
Fixed in: 2025
Severity: Medium 5.4 · Disclosed Jun 5, 2025
Stop Spammers Security | Block Spam Users, Comments, Forms <= 2024.4 - Cross-Site Request Forgery (CSRF) via sfs_process
Cross-site request forgery (CSRF) · CVE-2023-7065
Affected versions: ≤ 2024.4
Fixed in: 2024.5
Severity: Medium 5.4 · Disclosed May 3, 2024
Stop Spammers Security <= 2022.6 - Reflected Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2023-2488
Affected versions: ≤ 2022.6
Fixed in: 2023
Severity: Medium 6.1 · Disclosed May 15, 2023
Stop Spammers Security <= 2022.6 - Authenticated (Admin+) Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2023-2489
Affected versions: ≤ 2022.6
Fixed in: 2023
Severity: Medium 4.4 · Disclosed May 15, 2023
Stop Spammers Security <= 2022.5 - Unauthenticated PHP Object Injection
PHP object injection · CVE-2022-4120
Affected versions: ≤ 2022.5
Fixed in: 2022.6
Severity: Critical 9.8 · Disclosed Dec 5, 2022
Stop Spammers Security <= 2021.17 - Authenticated (Admin+) Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2021-24517
Affected versions: < 2021.18
Fixed in: 2021.18
Severity: Medium 4.8 · Disclosed Aug 9, 2021
Stop Spammers <= 2021.8 - Reflected Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2021-24245
Affected versions: < 2021.9
Fixed in: 2021.9
Severity: Medium 6.1 · Disclosed Apr 8, 2021
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| Stop Spammers Classic <= 2026.6 - Unauthenticated Stored Cross-Site Scripting via 'author' ParameterCross-site scripting (XSS) · CVE-2026-120477 | ≤ 2026.6 | 2026.7 | Medium 4.7 | Nov 6, 2026 |
| Stop Spammers Classic <= 2026.3 - Unauthenticated Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2026-48876 | ≤ 2026.3 | 2026.4 | High 7.2 | Jun 1, 2026 |
| Stop Spammers Classic <= 2026.1 - Cross-Site Request Forgery via Email AllowlistCross-site request forgery (CSRF) · CVE-2025-14795 | ≤ 2026.1 | 2026.2 | Medium 4.3 | Jan 27, 2026 |
| Anti-Spam: Spam Protection | Block Spam Users, Comments, Forms <= 2024.7 - Cross-Site Request Forgery to Multiple Administrative ActionsCross-site request forgery (CSRF) · CVE-2025-2935 | ≤ 2024.7 | 2025 | Medium 5.4 | Jun 5, 2025 |
| Stop Spammers Security | Block Spam Users, Comments, Forms <= 2024.4 - Cross-Site Request Forgery (CSRF) via sfs_processCross-site request forgery (CSRF) · CVE-2023-7065 | ≤ 2024.4 | 2024.5 | Medium 5.4 | May 3, 2024 |
| Stop Spammers Security <= 2022.6 - Reflected Cross-Site ScriptingCross-site scripting (XSS) · CVE-2023-2488 | ≤ 2022.6 | 2023 | Medium 6.1 | May 15, 2023 |
| Stop Spammers Security <= 2022.6 - Authenticated (Admin+) Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2023-2489 | ≤ 2022.6 | 2023 | Medium 4.4 | May 15, 2023 |
| Stop Spammers Security <= 2022.5 - Unauthenticated PHP Object InjectionPHP object injection · CVE-2022-4120 | ≤ 2022.5 | 2022.6 | Critical 9.8 | Dec 5, 2022 |
| Stop Spammers Security <= 2021.17 - Authenticated (Admin+) Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2021-24517 | < 2021.18 | 2021.18 | Medium 4.8 | Aug 9, 2021 |
| Stop Spammers <= 2021.8 - Reflected Cross-Site ScriptingCross-site scripting (XSS) · CVE-2021-24245 | < 2021.9 | 2021.9 | Medium 6.1 | Apr 8, 2021 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Nov 6, 2026.
Most common weaknesses in Stop Spammers Classic
Cross-site scripting (XSS)
6 issues
An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.
Cross-site request forgery (CSRF)
3 issues
If an administrator who is logged in opens a booby-trapped page elsewhere, the site can be made to change settings without their knowledge.
PHP object injection
1 issue
Specially crafted data makes the server behave in unintended ways. Combined with the right conditions, it can lead to a full takeover.
Frequently asked questions
Is Stop Spammers Classic safe to use?
Stop Spammers Classic is a well-known plugin with 20,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (2026.7) and turn on automatic updates.
How do I find which version of Stop Spammers Classic my site is running?
In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.
Could updating break my site?
Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.
Can I check all my other plugins too?
Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.
Check every plugin and theme automatically, every day
Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.
Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.
← All plugin vulnerabilitiesStop Spammers Classic on WordPress.org