SchemaEngine AI stored XSS in post content and excerpts
techlabpro1 SchemaEngine AI – AI Schema Markup, Reviews & Rich Snippets for SEO
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| techlabpro1 SchemaEngine AI – AI Schema Markup, Reviews & Rich Snippets for SEO |
| No fix yet |
Original description
The SchemaEngine AI – AI Schema Markup, Reviews & Rich Snippets for SEO plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'content/excerpt (REST wp/v2/posts) → stored in post_content/post_excerpt' parameter in all versions up to, and including, 3.1.3 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. A Contributor's entity-encoded payload survives save-time wp_kses filtering verbatim and is only decoded into raw script tags at render time via html_entity_decode(), meaning the injected script executes for every visitor — including authenticated Administrators — once an Editor publishes the post through the standard Contributor workflow.
From the CVE record · Wordfence