Wpspellcheck is a narrowly scoped spell-checking utility where the observed vulnerability footprint centers on its primary product and recurs around cross-site request forgery flaws that reflect the web-integration context of client-side text tools. Current exploitation activity and severity counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Wpspellcheck over time
Signals from CVEs in this vendor scope (4 CVEs).
4 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2024-22143HIGH Cross-Site Request Forgery (CSRF) vulnerability in WP Spell Check.This issue affects WP Spell Check: from n/a through 9.17. | Jan 31, 2024 | 8.8 | 24 | NO | NO |
CVE-2019-6027HIGH Cross-site request forgery (CSRF) vulnerability in WP Spell Check 7.1.9 and earlier allows remote attackers to hijack the authentication of administrators via unspecified vectors. | Dec 26, 2019 | 8.8 | 24 | NO | NO |
CVE-2022-2658MEDIUM The WP Spell Check WordPress plugin before 9.13 does not escape ignored words, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks e | Jan 16, 2023 | 4.8 | 19 | NO | NO |
CVE-2025-25111MEDIUM Cross-Site Request Forgery (CSRF) vulnerability in WP Spell Check WP Spell Check wp-spell-check allows Cross Site Request Forgery.This issue affects WP Spell Check: from n/a throug | Feb 7, 2025 | 5.4 | 17 | NO | NO |
Signals from CVEs in this vendor scope (4 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Wpspellcheck.
Media articles that mention a CVE ID that affects a product developed by Wpspellcheck — matched by CVE ID, not by vendor name.