CVE
SchemaEngine AI stored XSS via post content and excerpt fields
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
SchemaEngine AI, a WordPress plugin, has a stored cross-site scripting flaw. A remote attacker with contributor-level access or higher can inject scripts into posts without any user action, and those scripts run in the browser of anyone who views the published page, including administrators.
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.
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. 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
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-111371 (SchemaEngine AI <= 3.1.3 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'post_content' and 'post_excerpt' Parameters), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-111371 (entry last updated 2026-11-18):
Affected:
- techlabpro1 SchemaEngine AI – AI Schema Markup, Reviews & Rich Snippets for SEO: through 3.1.3
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-111371 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-111371 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/34aebb80-9e9a-43f6-982c-55b77f4f211e?source=cve
- https://plugins.trac.wordpress.org/browser/review-schema/tags/3.1.2/app/Modules/Schema/Models/Schema.php#L1537
- https://plugins.trac.wordpress.org/browser/review-schema/tags/3.1.2/app/Modules/Schema/Models/Schema.php#L169
- https://plugins.trac.wordpress.org/browser/review-schema/tags/3.1.2/app/Modules/Schema/Hooks/SchemaFrontend.php#L51
- https://plugins.trac.wordpress.org/browser/review-schema/tags/3.1.2/app/AI/SchemaRenderer.php#L89
- https://plugins.trac.wordpress.org/changeset?reponame=&old=3779685%40review-schema&new=3779685%40review-schema
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-111371
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-111371"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- techlabpro1 SchemaEngine AI – AI Schema Markup, Reviews & Rich Snippets for SEO
through 3.1.3
Evidence 8
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-111371
Is CVE-2026-111371 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-111371?
SchemaEngine AI – AI Schema Markup, Reviews & Rich Snippets for SEO: through 3.1.3.Source: cve.now feed data