Is CVE-2026-42749 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-42749 being exploited in the wild.

How severe is CVE-2026-42749?

High severity, with a CVSS score of 7.1, published 27 May 2026.

Is there a fix for CVE-2026-42749?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-42749 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-42749?

Check whether you run Themeisle Disable Comments for Any Post Types (Remove comments) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-42749: Themeisle Disable Comments for Any Post Types auth bypass

CVE-2026-42749 · Severity: high · CVSS 7.1 · Published 2026-05-27

A security vulnerability exists in a WordPress plugin used to manage and disable comments across a website. This flaw allows an attacker to bypass standard security checks during the password recovery process. If exploited, this could lead to unauthorized account access or service disruption, potentially compromising the site's administrative control.

Vendors: Themeisle.

Quick answers

Is CVE-2026-42749 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-42749 being exploited in the wild.
How severe is CVE-2026-42749?: High severity, with a CVSS score of 7.1, published 27 May 2026.
Which products and versions are affected?: Themeisle Disable Comments for Any Post Types (Remove comments) <= 1.3.0.
Is there a fix for CVE-2026-42749?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-42749 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-42749?: Check whether you run Themeisle Disable Comments for Any Post Types (Remove comments) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The Themeisle Disable Comments for Any Post Types (Remove comments) plugin for WordPress is vulnerable to an Authentication Bypass Using an Alternate Path or Channel (CWE-288). The flaw exists within the 'comments-plus' component and specifically impacts the password recovery workflow. An attacker with low-level privileges can exploit this alternate path to bypass authentication requirements. This can lead to unauthorized password resets or exploitation of the recovery mechanism. The issue affects all versions up to and including 1.3.0.

Affected products

Themeisle Disable Comments for Any Post Types (Remove comments) <= 1.3.0

Timeline

2026-05-27: disclosed
2026-05-27: advisory

References

https://patchstack.com/database/Wordpress/Plugin/comments-plus/vulnerability/wordpress-disable-comments-for-any-post-types-remove-comments-plugin-1-3-0-broken-authentication-vulnerability?_s_id=cve

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.