Stopwords For Comments
Approved changes feed: RSS · Atom
cpe:2.3:a:rndsand81:stopwords_for_comments:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Rndsand81 (86c157ee-6357-5f27-917e-92b5cb2b186c) |
|---|---|
| Product | Stopwords For Comments (6ad710a5-3540-50cd-9986-63513cbb29dd) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-15376 |
vulnerable | 2026-06-08 07:06:36.145980 |
Stopwords for comments <= 1.1 - Missing Authorization to Cross-Site Request Forgery
MEDIUM (4.3)
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-14T06:40:08.392Z
Updated: 2026-04-08T17:28:06.115Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.