CVE-2026-120552 json
SEO Engine <= 0.9.9 - Authenticated (Contributor+) Stored Cross-Site Scripting via Entity-Encoded Post Title via Strip-then-Decode in build_title()
published 6d ago modified 6d ago also EUVD-2026-115662
- cvss
- 6.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 9%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2026-120552 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
- 6d ago
Exploit prediction
0.20% chance of exploitation in the next 30 days, higher than 9% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N |
Affected products
- tigroumeow SEO Engine – Smart SEO with AI, Schema & Redirection for WordPress
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/454a05eb-fd4e-4125-abd0-7ba90ee2048a?source=cve
- plugins.trac.wordpress.org /browser/seo-engine/tags/0.9.9/classes/core.php#L744
- plugins.trac.wordpress.org /browser/seo-engine/tags/0.9.9/classes/core.php#L739
- plugins.trac.wordpress.org /browser/seo-engine/tags/0.9.9/classes/rest.php#L1381
- plugins.trac.wordpress.org /browser/seo-engine/tags/0.9.9/classes/rest.php#L164
- plugins.trac.wordpress.org /browser/seo-engine/tags/0.9.9/app/index.js
- plugins.trac.wordpress.org /changeset?old_path=/seo-engine/tags/0.9.9&new_path=/seo-engine/tags/1.0.0
Sources
- CVE List CVE-2026-120552
- NVD CVE-2026-120552
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.