Plugins · disable-comments · data as of 2026-11-01
Is Disable Comments safe? Known vulnerabilities and latest version
- Latest version
- 2.9.1
- Last updated
- 2026-10-25
- Active installs
- 1+ million
- Known issues on record
- 1
- Unpatched in latest
- 0
- Tested up to WP
- 7.1.4 · PHP 7.0+
Disable comments site-wide or by post type, delete existing comments in bulk, and block comment spam via REST API and XML-RPC. Multisite ready. — by WPDeveloper
What to do
- Update to the latest version (2.9.1). Anything older than 1.0.4 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.
With WP-CLI: wp plugin get disable-comments --field=version shows what you run; wp plugin update disable-comments updates it.
Check your version
Known vulnerabilities
1 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.
high 8.8 CVE-2014-2550 · published 2018-03-19
Cross-site request forgery (CSRF) in Disable Comments (older than 1.0.4)
- Affected
- older than 1.0.4
- Fixed in
- 1.0.4
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- advisory text · score by NVD
Details from the advisory
Cross-site request forgery (CSRF) vulnerability in the Disable Comments plugin before 1.0.4 for WordPress allows remote attackers to hijack the authentication of administrators for requests that enable comments via a request to the disable_comments_settings page to wp-admin/options-general.php.
NVD CVE-2014-2550wordpress.orgexchange.xforce.ibmcloud.comsecurity.dxw.com
Recent activity
- 2026-10-25 — latest release on wordpress.org (2.9.1).
- 2018-03-19 — Cross-site request forgery (CSRF) disclosed (CVE-2014-2550), fixed in 1.0.4.
Get an email when Disable Comments has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Disable Comments (disable-comments) is published or a fix ships. Unsubscribe in one click.
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/disable-comments (Plugins API), fetched 2026-11-01.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-01. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/disable-comments"><img src="https://laskyr.com/plugins/disable-comments/badge.svg" alt="Disable Comments vulnerability status"></a>