Skip to main content
← Vulnerabilities

SEO Engine <= 0.9.9 - Authenticated (Contributor+) Stored Cross-Site Scripting via Entity-Encoded Post Title via Strip-then-Decode in…

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

6.4MediumCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported
14Pcve.now Index 14 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure3/25Reachable over the network · Data gap: No advisory context yet
  • Reach?/20Reach: unknown (data gap). No tracked technology or package matched
  • Severity6.4/10CVSS 6.4
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 69 if added to CISA KEV
  • Would score about 64 if CISA's SSVC rates exploitation active
  • Would score about 33 if advisories confirm default setups are exposed

CVE-2026-120552 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.4 (medium) and affects SEO Engine – Smart SEO with AI, Schema & Redirection for WordPress; no fixed version is listed yet.

Published
Last modified
Published
Not listed in CISA KEV
0.20% · 9th percentile
14/100 · provisional
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

The SEO Engine WordPress plugin, which provides SEO, schema, and redirection features, is affected by a stored cross-site scripting flaw that lets contributor-level WordPress users inject scripts into post titles. The injected scripts can run in the browser of anyone who views the affected page, including administrators.

Read the original description

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.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • tigroumeow SEO Engine – Smart SEO with AI, Schema & Redirection for WordPress

    through 0.9.9

Evidence 7

  1. Link
  2. Link
  3. Link
  4. Link
  5. Link
Show all 7 sourcesShow fewer sources
  1. Link
  2. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

FAQ

Questions about CVE-2026-120552

Is CVE-2026-120552 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-120552?

SEO Engine – Smart SEO with AI, Schema & Redirection for WordPress: through 0.9.9.Source: cve.now feed data