Skip to main content
Menu
CVEs

SchemaEngine AI auth-free stored XSS in WebPage JSON-LD output

CVE-2026-96991Published November 21, 2026, updated

7.2HighCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported

Summary

The SchemaEngine AI – AI Schema Markup, Reviews & Rich Snippets for SEO plugin for WordPress has a stored cross-site scripting flaw in how comment content is inserted into its WebPage JSON-LD description. Remotely and without logging in, an attacker can inject script that runs in the browser of any user who visits an affected page, but only if that page shows the latest comments block with excerpts enabled.

Written by a model

Original description

The SchemaEngine AI – AI Schema Markup, Reviews & Rich Snippets for SEO plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content via WebPage JSON-LD Description in all versions up to, and including, 3.1.3 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires that the target page renders a core/latest-comments block with the displayExcerpt option enabled, causing comment content to be incorporated into the WebPage JSON-LD description output in wp_head.

What to do

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-96991 (SchemaEngine AI <= 3.1.3 - Unauthenticated Stored Cross-Site Scripting via Comment Content via WebPage JSON-LD Description), 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-96991 (entry last updated 2026-11-21):
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-96991 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-96991 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/d9f5d3e3-83eb-4c63-a479-def1b2f9da4c?source=cve
- https://plugins.trac.wordpress.org/browser/review-schema/tags/3.1.0/app/Modules/Schema/Models/Schema.php#L1566
- https://plugins.trac.wordpress.org/browser/review-schema/tags/3.1.0/app/Modules/Schema/Models/Schema.php#L169
- https://plugins.trac.wordpress.org/browser/review-schema/tags/3.1.0/app/Modules/Schema/Models/Schema.php#L157
- https://plugins.trac.wordpress.org/browser/review-schema/tags/3.1.0/app/Modules/Schema/Models/Schema.php#L808
- https://plugins.trac.wordpress.org/browser/review-schema/tags/3.1.0/app/Modules/Schema/Hooks/SchemaFrontend.php#L51
- 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-96991
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-96991"}.

Affected versions

cve.now Index

29Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.2/10CVSS 7.2
  • No patch5/5No patch listed yet

What would change the score

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

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 9

Questions about CVE-2026-96991

Is CVE-2026-96991 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-96991?

SchemaEngine AI – AI Schema Markup, Reviews & Rich Snippets for SEO: through 3.1.3.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.