Description
The Stopwords for comments plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.1. This is due to missing nonce validation on the 'set_stopwords_for_comments' and 'delete_stopwords_for_comments' functions. This makes it possible for unauthenticated attackers to add or delete stopwords via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Published: 2026-01-14
Score: 4.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Cross‑Site Request Forgery
Action: Immediate Patch
AI Analysis

Impact

The Stopwords for comments plugin permits unauthenticated users to trigger the addition or removal of stopwords via forged requests because nonce checks are omitted in the set_stopwords_for_comments and delete_stopwords_for_comments functions. This flaw, identified as a CSRF weakness, allows attackers to alter site content without authorization, potentially affecting the integrity of comment moderation and user experience.

Affected Systems

The vulnerability impacts the WordPress plugin Stopwords for comments, version 1.1 and all earlier releases. Administrators deploying these versions on any WordPress site are exposed.

Risk and Exploitability

With a CVSS score of 4.3 and an EPSS score below 1%, the technical severity is moderate but exploitation is unlikely, and the vulnerability is not listed in the CISA KEV catalog. The attack likely requires tricking a legitimate administrator into submitting a crafted request, making user awareness a key defense factor.

Generated by OpenCVE AI on April 21, 2026 at 00:25 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the Stopwords for comments plugin to the latest version where the nonce validation is restored.
  • If an upgrade is not immediately possible, block unauthenticated access to the set_stopwords_for_comments and delete_stopwords_for_comments endpoints using web‑application firewall rules or server‑side configuration changes.
  • Restrict the administrative capability to modify stopwords to users with the Administrator role and enforce CSRF protection on any submitted forms.
  • Educate site administrators to avoid clicking suspicious links and to verify the source of requests before proceeding with sensitive actions.

Generated by OpenCVE AI on April 21, 2026 at 00:25 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 15 Jan 2026 08:15:00 +0000

Type Values Removed Values Added
First Time appeared Wordpress
Wordpress wordpress
Vendors & Products Wordpress
Wordpress wordpress

Wed, 14 Jan 2026 20:15:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Wed, 14 Jan 2026 07:00:00 +0000

Type Values Removed Values Added
Description The Stopwords for comments plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.1. This is due to missing nonce validation on the 'set_stopwords_for_comments' and 'delete_stopwords_for_comments' functions. This makes it possible for unauthenticated attackers to add or delete stopwords via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Title Stopwords for comments <= 1.1 - Missing Authorization to Cross-Site Request Forgery
Weaknesses CWE-352
References
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N'}


Subscriptions

Wordpress Wordpress
cve-icon MITRE

Status: PUBLISHED

Assigner: Wordfence

Published:

Updated: 2026-04-08T17:28:06.115Z

Reserved: 2025-12-30T19:57:19.265Z

Link: CVE-2025-15376

cve-icon Vulnrichment

Updated: 2026-01-14T18:58:40.271Z

cve-icon NVD

Status : Deferred

Published: 2026-01-14T07:16:13.883

Modified: 2026-04-15T00:35:42.020

Link: CVE-2025-15376

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-04-21T00:30:22Z

Weaknesses