Description
The Newsletters WordPress plugin before 4.16 does not strictly compare its API authentication key, allowing unauthenticated attackers to bypass the API authentication via type juggling and perform privileged actions such as modifying subscriber records and sending emails, when the optional API has been enabled.
Published: 2026-08-08
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability resides in the Newsletters WordPress plugin versions prior to 4.16, where the API authentication key is compared loosely, allowing an attacker to perform type juggling against the key. This results in an unauthenticated bypass of the API authentication mechanism, granting unauthorized access to privileged actions such as modifying subscriber records and sending emails. The weakness is a classic authentication failure and can lead to data tampering, unauthorized notifications, and potentially broader compromise if the plugin is used in conjunction with other vulnerable components. The primary impact is loss of data integrity and confidential information, and the weakness is represented by CWE‑287.

Affected Systems

Any installation of the Newsletters WordPress plugin prior to version 4.16 where the optional API feature is enabled is affected. The vendor is listed as "Unknown:Newsletters" in CNA data, so the scope is limited to WordPress sites running this particular plugin revision.

Risk and Exploitability

The EPSS score is not available, and the vulnerability is not listed in CISA KEV, indicating no known widespread exploitation yet. However, the attack vector is inferred to be over the network via HTTP requests to the plugin’s API endpoint, requiring the optional API to be enabled. Given the nature of the flaw – an authentication bypass that allows arbitrary state changes – the potential impact is high. The lack of a public exploit does not diminish the inherent risk, especially for sites with sensitive user data or those relying on the plugin for critical mailing lists.

Generated by OpenCVE AI on August 8, 2026 at 07:25 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update the Newsletters plugin to version 4.16 or later to apply the fixed API key comparison logic.
  • Disable the optional API feature if an update cannot be applied immediately, removing the vulnerable endpoint from exposure.
  • Review subscriber records and outbound email logs for any unauthorized modifications or unexpected email activity, and correct them as needed.
  • Consider enforcing stricter input validation or adding an additional API key check to minimize the risk of type juggling attacks while a permanent fix is deployed.

Generated by OpenCVE AI on August 8, 2026 at 07:25 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 08 Aug 2026 07:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-287

Sat, 08 Aug 2026 06:30:00 +0000

Type Values Removed Values Added
Description The Newsletters WordPress plugin before 4.16 does not strictly compare its API authentication key, allowing unauthenticated attackers to bypass the API authentication via type juggling and perform privileged actions such as modifying subscriber records and sending emails, when the optional API has been enabled.
Title Newsletters < 4.16 - Unauthenticated API Authentication Bypass via Type Juggling
References

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: WPScan

Published:

Updated: 2026-08-08T06:00:10.712Z

Reserved: 2026-07-20T09:09:41.544Z

Link: CVE-2026-16269

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-08T07:30:17Z

Weaknesses