LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1293: Yoast SEO <= 26.8 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'yoast-schema' Block Attribute

The Yoast SEO – Advanced SEO with real-time guidance and built-in AI plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the the `yoast-schema` block attribute in all versions up to, and including, 26.8 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.

MediumCVSS 6.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-1293 affects the Yoast SEO WordPress plugin through version 26.8. A logged-in user with Contributor or higher privileges could store script content in a page through the yoast-schema block attribute. That script would run when someone views the affected page, creating risk to site users and administrators.

Executive priority

Treat as a near-term web security task, not an emergency unless untrusted contributors exist. Prioritize public-facing WordPress sites with many content users or weak account governance.

Technical view

This is authenticated stored cross-site scripting, CWE-79, caused by insufficient input sanitization and output escaping around the yoast-schema block attribute. The CVSS 3.1 score is 6.4 with low privileges required, network access, changed scope, and low confidentiality and integrity impact.

Likely exposure

Exposure is most relevant to WordPress sites running Yoast SEO up to and including 26.8, especially where untrusted or numerous users have Contributor-level publishing access or higher.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. Exploitation requires an authenticated account with Contributor or higher privileges and depends on malicious content being saved to a page viewed by others.

Researcher notes

The source bundle identifies the vulnerable attribute and related WordPress plugin code locations, but does not provide a named fixed version. The affected data also contains an inconsistent version entry, so rely on the narrative stating all versions through 26.8.

Mitigation direction

  • Identify WordPress sites using Yoast SEO version 26.8 or earlier.
  • Restrict Contributor and higher roles to trusted users only.
  • Review vendor and Wordfence guidance for the fixed version or official remediation.
  • Update the plugin when an official patched release is confirmed.
  • Remove or review suspicious content using yoast-schema block attributes.

Validation and detection

  • Inventory Yoast SEO versions across WordPress environments.
  • Confirm whether any site is running version 26.8 or earlier.
  • Review users with Contributor, Author, Editor, or Administrator roles.
  • Inspect recent page edits by lower-privileged authenticated users.
  • Check security monitoring for suspicious stored script activity.
Prepared
Confidence
medium
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-1293 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N3.12.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.4Medium
CVSS 3.1 vector shape for CVE-2026-1293Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
yoastYoast SEO – Advanced SEO with real-time guidance and built-in AI0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.