CVE-2026-4142 json
Sentence To SEO (keywords, description and tags) <= 1.0 - Authenticated (Administrator+) Stored Cross-Site Scripting via 'Permanent keywords' Field
published 6mo ago modified 4mo ago also EUVD-2026-24684
- cvss
- 4.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 25%
- public exploits
- 0
- none known
Summary
The Sentence To SEO (keywords, description and tags) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'Permanent keywords' field in all versions up to and including 1.0. This is due to insufficient input sanitization and output escaping. The plugin reads user input via filter_input_array(INPUT_POST) which applies no HTML sanitization (FILTER_DEFAULT), stores it unsanitized to the WordPress options table via update_option(), and then outputs the stored value directly into a textarea element without any escaping using PHP short echo tags (<?= ?>). An attacker can break out of the textarea element using a closing </textarea> tag and inject arbitrary HTML/JavaScript. This makes it possible for authenticated attackers, with administrator-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses the plugin's settings page.
Is CVE-2026-4142 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 6mo ago
Exploit prediction
0.33% chance of exploitation in the next 30 days, higher than 25% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.4 | CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N |
Affected products
- eazyserver Sentence To SEO (keywords, description and tags)
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/7d11b2db-d097-433f-923c-f49ef2951c0e?source=cve
- plugins.trac.wordpress.org /browser/sentence-to-seo/trunk/index.php#L81
- plugins.trac.wordpress.org /browser/sentence-to-seo/tags/1.0/index.php#L81
- plugins.trac.wordpress.org /browser/sentence-to-seo/trunk/index.php#L50
- plugins.trac.wordpress.org /browser/sentence-to-seo/tags/1.0/index.php#L50
- plugins.trac.wordpress.org /browser/sentence-to-seo/trunk/index.php#L262
- plugins.trac.wordpress.org /browser/sentence-to-seo/tags/1.0/index.php#L262
- plugins.trac.wordpress.org /browser/sentence-to-seo/trunk/index.php#L87
- plugins.trac.wordpress.org /browser/sentence-to-seo/tags/1.0/index.php#L87
- plugins.trac.wordpress.org /browser/sentence-to-seo/trunk/index.php#L75
- plugins.trac.wordpress.org /browser/sentence-to-seo/tags/1.0/index.php#L75
Sources
- CVE List CVE-2026-4142
- NVD CVE-2026-4142
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.