PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-111402 Tribulant Software CVE debrief

A SQL Injection vulnerability exists in the Newsletters plugin for WordPress, affecting versions from n/a through 4.18.1. This issue, identified as CVE-2026-111402, has a CVSS score of 9.3, indicating critical severity. The vulnerability allows for SQL Injection due to improper neutralization of special elements used in an SQL command. This critical vulnerability in the Newsletters plugin for WordPress can be exploited remotely without authentication, potentially allowing attackers to extract or modify sensitive data. Defenders should prioritize verifying exposure, especially for versions prior to 4.18.1, and assess potential SQL Injection attacks. The CVE record and NVD entry are

Vendor
Tribulant Software
Product
Newsletters
CVSS
CRITICAL 9.3
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-24
Original CVE updated
2026-10-24
Advisory published
2026-10-24
Advisory updated
2026-10-24

Who should care

Defenders responsible for WordPress installations using the Newsletters plugin, especially those using versions prior to 4.18.1, should assess their exposure and take appropriate remediation steps. This includes updating the plugin to a secure version and monitoring for potential SQL Injection attacks.

Why it matters

CVE-2026-111402 represents a critical SQL Injection vulnerability in the Newsletters plugin for WordPress. Defenders should prioritize verification of exposure, especially for versions prior to 4.18.1, and assess potential SQL Injection attacks. Remediation involves updating the plugin and implementing security measures like WAFs.

  • Potential for remote exploitation without authentication, allowing for data extraction or modification.
  • High CVSS score indicating critical severity, suggesting immediate attention is required.
  • Possible impact on data integrity and confidentiality if exploited.

Technical summary

The Newsletters plugin for WordPress, versions from n/a through 4.18.1, is vulnerable to SQL Injection. This vulnerability is due to improper neutralization of special elements used in an SQL command. The CVSS score for this vulnerability is 9.3, indicating critical severity. The vulnerability can be exploited remotely without authentication, allowing attackers to potentially extract or modify sensitive data.

Defensive priority

Defenders should prioritize verifying exposure of the Newsletters plugin in their environments, especially if versions prior to 4.18.1 are in use, and assess the potential for SQL Injection attacks.

Recommended defensive actions

  • Verify the version of the Newsletters plugin in use and ensure it is updated to a version beyond 4.18.1 if possible.
  • Review database configurations and monitor for suspicious SQL queries that could indicate exploitation attempts.
  • Implement additional security measures such as web application firewalls (WAFs) to detect and prevent SQL Injection attacks.

Evidence notes

The CVE record and NVD entry provide details on the SQL Injection vulnerability in the Newsletters plugin. However, specific details about exploitation or affected systems are not provided in the source corpus.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-111402 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-111402

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-111402 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-111402

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.