SEO Engine <= 0.9.9 - Authenticated (Contributor+) Stored Cross-Site Scripting via Entity-Encoded Post Title via Strip-then-Decode in build_title()
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| tigroumeow | SEO Engine – Smart SEO with AI, Schema & Redirection for WordPress | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Tigroumeow | Seo Engine – Smart Seo With Ai, Schema & Redirection For Wordpress |
|
||||||||
| Wordpress-extensions | Seo Engine |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.198% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Tigroumeow
Tigroumeow seo Engine – Smart Seo With Ai, Schema & Redirection For Wordpress Wordpress-extensions Wordpress-extensions seo Engine |
|
| Vendors & Products |
Tigroumeow
Tigroumeow seo Engine – Smart Seo With Ai, Schema & Redirection For Wordpress Wordpress-extensions Wordpress-extensions seo Engine |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | SEO Engine <= 0.9.9 - Authenticated (Contributor+) Stored Cross-Site Scripting via Entity-Encoded Post Title via Strip-then-Decode in build_title() | |
| Weaknesses | CWE-79 | |
| References |
|
|
| Metrics |
cvssV3_1
|