WordPress plugin · Updated daily · Source: Wordfence Intelligence

Subscribe to Comments vulnerabilities: affected versions and fixes

Subscribe to Comments has 10,000+ active installs. Here are its publicly disclosed vulnerabilities, whether your version is affected, and what to do now.

Subscribe to Comments at a glance

  • 7 publicly disclosed vulnerabilities, 1 of them rated High or Critical. The most recent was disclosed on Oct 20, 2026.
  • Ranked #1577 by popularity on WordPress.org (10,000+ active installs).
  • The latest version is 2.3.3 (released Oct 6, 2026). The most recent security fix shipped in 2.3.3.
  • 1 vulnerability has no fix yet. Check the list below to see whether it affects how you use the plugin.
  • The first thing to do: update to the latest version and turn on automatic updates.

Check your Subscribe to Comments version

Enter the Subscribe to Comments 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 “Subscribe to Comments”, 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.

View the plugin on wordpress.orgGet a free in-depth scan

How to check whether your site is affected

  1. 1

    Find your version

    In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Subscribe to Comments”.

  2. 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. 3

    Update

    Click “Update now” to move to the latest version (2.3.3). Taking a backup first is a good idea.

  4. 4

    Turn on automatic updates

    On the same screen, click “Enable auto-updates” so future fixes are installed automatically.

Known Subscribe to Comments vulnerabilities

  • Subscribe to Comments 2.3 - 2.3.2 - Authenticated (Author+) Arbitrary Email Header Injection

    Other weakness · CVE-2026-91831

    Affected versions: ≥ 2.3, ≤ 2.3.2

    Fixed in: 2.3.3

    Severity: Medium 4.3 · Disclosed Oct 20, 2026

  • Subscribe to Comments <= 2.3.2 - Unauthenticated Information Exposure

    Information disclosure · CVE-2026-91830

    Affected versions: ≤ 2.3.2

    Fixed in: 2.3.3

    Severity: Medium 5.3 · Disclosed Oct 13, 2026

  • Subscribe to Comments <= 2.3.2 - Reflected Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2026-91829

    Affected versions: ≤ 2.3.2

    Fixed in: 2.3.3

    Severity: Medium 6.1 · Disclosed Oct 9, 2026

  • Subscribe to Comments <= 2.3.1 - Authenticated (Author+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2026-66706

    Affected versions: ≤ 2.3.1

    Fixed in: No fix yet

    Severity: Medium 5.4 · Disclosed Aug 6, 2026

  • Subscribe to Comments <= 2.3 - Reflected Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2024-8792

    Affected versions: ≤ 2.3

    Fixed in: 2.3.1

    Severity: Medium 6.1 · Disclosed Oct 29, 2024

  • Subscribe to Comments <= 2.1.2 - Local File Includion

    Other weakness · CVE-2015-10133

    Affected versions: ≤ 2.1.2

    Fixed in: 2.3

    Severity: High 7.2 · Disclosed Jul 15, 2015

  • Subscribe to Comments <= 2.0.7 - Reflected Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2006-10001

    Affected versions: ≤ 2.0.7

    Fixed in: 2.0.8

    Severity: Medium 6.1 · Disclosed Sep 17, 2006

Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Oct 20, 2026.

Most common weaknesses in Subscribe to Comments

Cross-site scripting (XSS)

4 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.

Information disclosure

1 issue

Data that should stay private, such as user details or configuration values, can be read from outside.

Frequently asked questions

Is Subscribe to Comments safe to use?

Subscribe to Comments is a well-known plugin with 10,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 (2.3.3) and turn on automatic updates. That said, 1 issue has no fix yet, so check the list below.

How do I find which version of Subscribe to Comments 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 vulnerabilitiesSubscribe to Comments on WordPress.org