Which versions of Sentence To SEO (keywords, description and tags) are vulnerable?

Known issues on record (newest first): Cross-site request forgery (CSRF) (1.0 and older); Stored cross-site scripting (XSS) (1.0 and older). The full list with sources is on this page.

What should I do if my Sentence To SEO (keywords, description and tags) is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update sentence-to-seo). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · sentence-to-seo · data as of 2026-11-04

Is Sentence To SEO (keywords, description and tags) safe? Known vulnerabilities and latest version

Q: Is Sentence To SEO (keywords, description and tags) safe to use?

Laskyr does not give safety verdicts. Sentence To SEO (keywords, description and tags) is closed on wordpress.org. Closed on 2026-04-15 (reason given: Security Issue). Closed plugins get no updates through WordPress, so new security holes will not be fixed for you. Keep Sentence To SEO (keywords, description and tags) on the latest version and remove it if you do not use it.

Status: Closed 2026-04-15
Known issues on record: 2
Unpatched in latest: 0

What to do

Replace it. A closed plugin gets no updates through WordPress, so any hole found from now on stays open.
Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deleting removes its files; deactivating alone leaves them on the server.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.

With WP-CLI, once you have a replacement: wp plugin deactivate sentence-to-seo && wp plugin delete sentence-to-seo

Check your version

Known vulnerabilities

2 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version. 2 record(s) do not state which versions are affected.

medium 6.1 CVE-2026-6391 · published 2026-05-20

Cross-site request forgery (CSRF) in Sentence To SEO (keywords, description and tags) (1.0 and older)

Affected: 1.0 and older
Fixed in: unknown
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

The Sentence To SEO (keywords, description and tags) plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0. This is due to missing or incorrect nonce validation on the create_admin_page() function. This makes it possible for unauthenticated attackers to inject malicious web scripts and update plugin settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

NVD CVE-2026-6391 Wordfence advisory Plugin source

medium 4.4 CVE-2026-4142 · published 2026-04-22

Stored cross-site scripting (XSS) in Sentence To SEO (keywords, description and tags) (1.0 and older)

Affected: 1.0 and older
Fixed in: unknown
Access needed (per CVSS): Needs an admin-level account
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

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.

NVD CVE-2026-4142 Wordfence advisory Plugin source

Recent activity

2026-04-15 — closed on wordpress.org (Security Issue).
2026-05-20 — Cross-site request forgery (CSRF) disclosed (CVE-2026-6391), fix version not stated.
2026-04-22 — Stored cross-site scripting (XSS) disclosed (CVE-2026-4142), fix version not stated.

Free. We check the CVE feeds every day and email you only when a new issue for Sentence To SEO (keywords, description and tags) (sentence-to-seo) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Cross-site request forgery (CSRF) (1) · Cross-site scripting (XSS) (1)

Where this data comes from

Version, last update, installs, closure: wordpress.org/plugins/sentence-to-seo (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/sentence-to-seo"><img src="https://laskyr.com/plugins/sentence-to-seo/badge.svg" alt="Sentence To SEO (keywords, description and tags) vulnerability status"></a>

← Check another plugin · Free hacked-site scan