LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24591: WordPress Turn Yoast SEO FAQ Block to Accordion plugin <= 1.0.6 - Cross Site Scripting (XSS) vulnerability

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in yasir129 Turn Yoast SEO FAQ Block to Accordion faq-schema-block-to-accordion allows Stored XSS.This issue affects Turn Yoast SEO FAQ Block to Accordion: from n/a through <= 1.0.6.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This WordPress plugin vulnerability could let a logged-in user store malicious script content that later runs in another user’s browser. For a business, the main concern is compromise of site admin sessions, content integrity, or visitor trust if the vulnerable plugin is used.

Executive priority

Treat as a standard-priority web application remediation item if the plugin is present. Escalate priority for public sites with multiple contributors, customer-facing content, or sensitive administrator sessions.

Technical view

CVE-2026-24591 is a stored cross-site scripting issue in yasir129 Turn Yoast SEO FAQ Block to Accordion, package faq-schema-block-to-accordion, affecting versions through 1.0.6. CVSS 3.1 is 6.5 with network access, low complexity, low privileges, required user interaction, and changed scope.

Likely exposure

Exposure is limited to WordPress sites with the Turn Yoast SEO FAQ Block to Accordion plugin installed at version 1.0.6 or earlier. The source bundle does not identify affected hosting providers, themes, or default WordPress installations.

Exploitation context

The CVSS vector indicates exploitation requires a low-privileged account and user interaction. The source bundle does not report active exploitation, public exploit availability, or CISA KEV listing.

Researcher notes

Evidence supports stored XSS and affected versions through 1.0.6. The provided sources do not name a fixed version, detailed vulnerable parameter, proof of concept, or exploitation in the wild. Avoid assuming broader plugin ecosystem impact.

Mitigation direction

  • Inventory WordPress sites for the faq-schema-block-to-accordion plugin.
  • Check the installed plugin version and identify versions 1.0.6 or earlier.
  • Review vendor, WordPress plugin, or Patchstack guidance for an official fix.
  • Disable or remove the plugin where it is not required.
  • Restrict low-privileged content-editing access until remediation is confirmed.

Validation and detection

  • Confirm whether the plugin is installed on each WordPress instance.
  • Record installed plugin version and compare against affected versions through 1.0.6.
  • Review recent content changes by low-privileged users.
  • Check security monitoring for unexpected script execution or suspicious admin activity.
  • Verify remediation status against vendor or Patchstack advisories.
Prepared
Confidence
medium
Sources
3

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-24591 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.5 (3.1)
Known Exploited
No
Published

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

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
2Source 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.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L2.33.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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
yasir129Turn Yoast SEO FAQ Block to Accordionfaq-schema-block-to-accordion, 0unaffected
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.