Live › vulnerability › CVE-2026-120552
The SEO Engine WordPress plugin up to and including 0.9.9 fails to sanitize the title parameter, so output is not escaped. An authenticated contributor can store a script in a page title that runs in the browser of anyone who opens that page.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-03 05:48 UTC. All times on this page are UTC.
Sites running the SEO Engine plugin at version 0.9.9 or earlier are exposed. Exploitation requires a logged-in account with Contributor role or higher that can create or edit posts, so sites with only trusted editors or no multi-user publishing are at lower risk.
No product ranges from the sources yet.
wp plugin get <plugin-slug> --field=version0.9.9; the exact fixed version is unknown from the sourcesEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
The SEO Engine – Smart SEO with AI, Schema & Redirection for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'title' parameter in all versions up to, and including, 0.9.9 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. WordPress core's wp_filter_kses (applied via title_save_pre for Contributors and Authors) strips literal tag markup on save but leaves HTML-entity-encoded payloads intact in the database, meaning entity-encoded XSS payloads stored via the standard WordPress REST API (POST /wp-json/wp/v2/posts) are not neutralized before reaching the vulnerable sink.
This page as .md · .json · in your agent: get_signal("CVE-2026-120552")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.