Xagio SEO & AEO stored cross-site scripting in 'title' shortcode attribute
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
The Xagio SEO & AEO – AI SEO for Google Rankings & AI Visibility plugin for WordPress has a stored cross-site scripting flaw in its 'title' shortcode attribute. Remotely, an attacker with contributor-level login or higher can save scripts into pages that then run in the browser of anyone who opens the injected page.
Written by a model
Original description
The Xagio SEO & AEO – AI SEO for Google Rankings & AI Visibility plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'title' parameter in all versions up to, and including, 7.1.0.51 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. The wp_kses_post filter applied at save time does not strip angle-bracket-free double-quote breakout payloads in shortcode attribute values, leaving injected event handlers intact in stored post content.
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-126715 (Xagio SEO & AEO <= 7.1.0.51 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'title' Shortcode Attribute), 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-126715 (entry last updated 2026-11-20):
Affected:
- xagio Xagio SEO & AEO – AI SEO for Google Rankings & AI Visibility: through 7.1.0.51
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-126715 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126715 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/1b9ca808-fad0-42df-a8f3-016badb66076?source=cve
- https://plugins.trac.wordpress.org/browser/xagio-seo/tags/7.1.0.50/modules/linkmanagement/models/xagio_shortcodes.php#L780
- https://plugins.trac.wordpress.org/browser/xagio-seo/tags/7.1.0.50/modules/linkmanagement/models/xagio_shortcodes.php#L763
- https://plugins.trac.wordpress.org/browser/xagio-seo/tags/7.1.0.50/modules/linkmanagement/models/xagio_shortcodes.php#L654
- https://plugins.trac.wordpress.org/changeset?reponame=&old=3798382%40xagio-seo&new=3798382%40xagio-seo
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-126715
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-126715"}.Affected versions
- xagio Xagio SEO & AEO – AI SEO for Google Rankings & AI Visibilitythrough 7.1.0.51
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
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 7
Questions about CVE-2026-126715
Is CVE-2026-126715 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-126715?
Xagio SEO & AEO – AI SEO for Google Rankings & AI Visibility: through 7.1.0.51.
Source: cve.now feed data
Related
- CVE-2024-13807Xagio SEO <= 7.1.0.5 - Unauthenticated Sensitive Information Exposure via Unprotected Back-Up Files
- CVE-2025-3302Xagio SEO <= 7.1.0.16 - Unauthenticated Stored Cross-Site Scripting via 'HTTP_REFERER'
- CVE-2025-14438Xagio SEO <= 7.1.0.30 - Authenticated (Subscriber+) Server-Side Request Forgery
- CVE-2026-94567NukeViet CMS: Stored XSS via SVG upload: the sanitizer is blind to markup hidden inside an internal DTD entity
- CVE-2026-94565NukeViet CMS: Unauthenticated Stored XSS in the Contact module
- CVE-2026-54064NukeViet CMS: Multiple Anti-XSS Filter Bypasses Leading to Stored XSS in News Module
No corrections so far. Something wrong on this page? Report an error.