WordPress plugin · Updated daily · Source: Wordfence Intelligence

Comments vulnerabilities: affected versions and fixes

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

Comments at a glance

  • 29 publicly disclosed vulnerabilities, 10 of them rated High or Critical. The most recent was disclosed on Nov 13, 2026.
  • Ranked #639 by popularity on WordPress.org (60,000+ active installs).
  • The latest version is 7.7.0 (released Nov 12, 2026). The most recent security fix shipped in 7.7.0.
  • 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 Comments version

Enter the 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 “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 “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 (7.7.0). 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 Comments vulnerabilities (latest 25 of 29)

  • Comments – wpDiscuz <= 7.6.75 - Unauthenticated Stored Cross-Site Scripting

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

    Affected versions: ≤ 7.6.75

    Fixed in: 7.7.0

    Severity: High 7.2 · Disclosed Nov 13, 2026

  • Comments – wpDiscuz <= 7.6.73 - Unauthenticated Stored Cross-Site Scripting

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

    Affected versions: ≤ 7.6.73

    Fixed in: 7.6.74

    Severity: High 7.2 · Disclosed Nov 2, 2026

  • Comments – wpDiscuz < 7.6.66 - Unauthenticated SQL Injection

    SQL injection · CVE-2026-19704

    Affected versions: < 7.6.66

    Fixed in: 7.6.66

    Severity: High 7.5 · Disclosed Sep 2, 2026

  • Comments <= 7.6.56 - Unauthenticated Stored Cross-Site Scripting via 'Website' Field

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

    Affected versions: ≤ 7.6.56

    Fixed in: 7.6.57

    Severity: High 7.2 · Disclosed Jul 2, 2026

  • Comments – wpDiscuz <= 7.6.46 - Authenticated (Admin+) Stored Cross-Site Scripting

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

    Affected versions: ≤ 7.6.46

    Fixed in: 7.6.47

    Severity: Medium 4.4 · Disclosed Mar 12, 2026

  • wpDiscuz <= 7.6.42 - Unauthenticated Insecure Direct Object Reference

    Missing authorization · CVE-2025-68997

    Affected versions: ≤ 7.6.42

    Fixed in: 7.6.44

    Severity: Medium 5.3 · Disclosed Dec 25, 2025

  • Comments – wpDiscuz <= 7.6.39 - Unauthenticated Authentication Bypass Through Account Takeover

    Missing authorization · CVE-2025-13820

    Affected versions: ≤ 7.6.39

    Fixed in: 7.6.40

    Severity: High 8.1 · Disclosed Dec 11, 2025

  • wpDiscuz <= 7.6.33 - Missing Authorization

    Missing authorization · CVE-2025-59591

    Affected versions: ≤ 7.6.33

    Fixed in: 7.6.34

    Severity: Medium 4.3 · Disclosed Sep 22, 2025

  • Comments – wpDiscuz <= 7.6.24 - Authentication Bypass via WordPress.com OAuth provider

    Missing authorization · CVE-2024-9488

    Affected versions: ≤ 7.6.24

    Fixed in: 7.6.25

    Severity: Critical 9.8 · Disclosed Oct 24, 2024

  • Comments – wpDiscuz <= 7.6.21 - Unauthenticated HTML Injection

    Other weakness · CVE-2024-6704

    Affected versions: ≤ 7.6.21

    Fixed in: 7.6.22

    Severity: Medium 5.3 · Disclosed Aug 1, 2024

  • Comments – wpDiscuz <= 7.6.18 - Authenticated (Contributor+) Stored Cross-Site Scripting

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

    Affected versions: ≤ 7.6.18

    Fixed in: 7.6.19

    Severity: Medium 6.4 · Disclosed Jun 6, 2024

  • wpDiscuz <= 7.6.15 - Authenticated (Author+) Stored Cross-Site Scripting via Uploaded Image Alternative Text

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

    Affected versions: ≤ 7.6.15

    Fixed in: 7.6.16

    Severity: Medium 6.4 · Disclosed Apr 22, 2024

  • wpDiscuz <= 7.6.12 - Authenticated (Administrator+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2023-51691

    Affected versions: ≤ 7.6.12

    Fixed in: 7.6.13

    Severity: Medium 4.4 · Disclosed Nov 17, 2023

  • wpDiscuz <= 7.6.11 - Cross-Site Request Forgery

    Cross-site request forgery (CSRF) · CVE-2023-47775

    Affected versions: ≤ 7.6.11

    Fixed in: 7.6.12

    Severity: Medium 4.3 · Disclosed Nov 14, 2023

  • wpDiscuz <= 7.6.11 - Unauthenticated Stored Cross-Site Scripting via Comment Uploaded Image Filename

    Cross-site scripting (XSS) · CVE-2023-47185

    Affected versions: ≤ 7.6.11

    Fixed in: 7.6.12

    Severity: High 7.2 · Disclosed Oct 31, 2023

  • wpDiscuz <= 7.6.10 - Unauthenticated Content Injection

    Other weakness · CVE-2023-46310

    Affected versions: ≤ 7.6.10

    Fixed in: 7.6.11

    Severity: Medium 4.3 · Disclosed Oct 22, 2023

  • wpDiscuz <= 7.6.3 - Authenticated(Author+) Insecure Direct Object Reference

    Missing authorization · CVE-2023-46311

    Affected versions: ≤ 7.6.3

    Fixed in: 7.6.4

    Severity: Low 2.7 · Disclosed Oct 22, 2023

  • wpDiscuz <= 7.6.10 - Insufficient Authorization to Comment Submission on Deleted Posts

    Missing authorization · CVE-2023-46309

    Affected versions: ≤ 7.6.10

    Fixed in: 7.6.11

    Severity: Medium 5.3 · Disclosed Oct 20, 2023

  • wpDiscuz <= 7.6.3 - Missing Authorization via AJAX actions

    Missing authorization · CVE-2023-45760

    Affected versions: ≤ 7.6.3

    Fixed in: 7.6.4

    Severity: Medium 5.4 · Disclosed Oct 12, 2023

  • wpDiscuz <= 7.6.5 - Unauthenticated SQL Injection

    SQL injection

    Affected versions: < 7.6.6

    Fixed in: 7.6.6

    Severity: High 8.8 · Disclosed Sep 18, 2023

  • wpDiscuz <= 7.6.3 - Insecure Direct Object Reference to Post Rating Increase/Decrease

    Missing authorization · CVE-2023-3998

    Affected versions: ≤ 7.6.3

    Fixed in: 7.6.4

    Severity: Medium 5.3 · Disclosed Sep 12, 2023

  • wpDiscuz <= 7.6.3 - Insecure Direct Object Reference to Comment Rating Increase/Decrease

    Missing authorization · CVE-2023-3869

    Affected versions: ≤ 7.6.3

    Fixed in: 7.6.4

    Severity: Medium 5.3 · Disclosed Sep 12, 2023

  • Comments – wpDiscuz <= 7.4.2 - Insecure Direct Object References

    Missing authorization · CVE-2022-43492

    Affected versions: ≤ 7.4.2

    Fixed in: 7.5

    Severity: Medium 5.4 · Disclosed Oct 28, 2022

  • Comments - wpDiscuz <= 7.3.11 Sensitive Information Disclosure

    Information disclosure · CVE-2022-23984

    Affected versions: ≤ 7.3.11

    Fixed in: 7.3.12

    Severity: Low 3.7 · Disclosed Feb 10, 2022

  • Comments - wpDiscuz <= 7.3.3 - Arbitrary Comment Addition/Edition/Deletion by Cross-Site Request Forgery

    Cross-site request forgery (CSRF) · CVE-2021-24806

    Affected versions: < 7.3.4

    Fixed in: 7.3.4

    Severity: Medium 4.3 · Disclosed Oct 11, 2021

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

Most common weaknesses in Comments

Cross-site scripting (XSS)

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

Missing authorization

10 issues

Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.

SQL injection

3 issues

Input such as a form field can be used to rewrite the queries the site sends to its database. Attackers use it to pull out customer, member or order data.

Frequently asked questions

Is Comments safe to use?

Comments is a well-known plugin with 60,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 (7.7.0) and turn on automatic updates.

How do I find which version of 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 vulnerabilitiesComments on WordPress.org