LiveActive security incident?Get immediate response
CVE Record

CVE-2023-26536: WordPress Sp*tify Play Button for WordPress Plugin <= 2.05 is vulnerable to Cross Site Scripting (XSS)

Auth. (contributor+) Cross-Site Scripting (XSS) vulnerability in Jonk @ Follow me Darling Sp*tify Play Button for WordPress plugin <= 2.05 versions.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-26536 is a cross-site scripting issue in the Sp*tify Play Button for WordPress plugin up to version 2.05. A logged-in contributor or higher could place unsafe content that may run in another user's browser after interaction. It matters most on sites with many authors or less-trusted content contributors.

Executive priority

Treat this as a moderate-priority WordPress plugin risk. It is not supported as actively exploited by the provided sources, but affected public sites with many contributors should be reviewed promptly because browser-side compromise can affect administrators and visitors.

Technical view

The source bundle identifies CWE-79 in Jonk @ Follow me Darling's WordPress plugin package spotify-play-button-for-wordpress. CVSS 3.1 is 6.5 with network access, low complexity, low privileges, required user interaction, changed scope, and low confidentiality, integrity, and availability impact. The sources do not name a fixed version.

Likely exposure

Exposure is likely limited to WordPress sites running Sp*tify Play Button for WordPress version 2.05 or earlier, especially where contributor-level accounts are available to multiple users. Sites without this plugin, or without untrusted contributor access, are less likely to be exposed.

Exploitation context

The provided sources do not show active exploitation, and the CVE is not marked KEV. Exploitation requires authenticated contributor-level or higher access and user interaction, so the practical risk depends on account hygiene, author trust, and who may view affected content.

Researcher notes

Evidence is enough to classify the issue as authenticated XSS, but incomplete for exact fixed-version guidance. Avoid assuming exploit availability or storage behavior from the bundle alone. Focus validation on plugin presence, version, contributor permissions, and vendor advisory updates.

Mitigation direction

  • Inventory WordPress sites for spotify-play-button-for-wordpress version 2.05 or earlier.
  • Check vendor or Patchstack guidance for a fixed version or official mitigation.
  • Disable or remove the plugin where it is not business-critical.
  • Restrict contributor-level access to trusted users only.
  • Review recent contributor activity for unexpected embedded content.

Validation and detection

  • Confirm whether the plugin is installed on production WordPress sites.
  • Record installed plugin versions and compare against the affected range.
  • Verify contributor, author, and editor accounts are still required.
  • Check security monitoring for suspicious script execution reports.
  • Document whether vendor remediation guidance is available.
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-2023-26536 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-2023-26536Attack 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
Jonk @ Follow me DarlingSp*tify Play Button for WordPressspotify-play-button-for-wordpress, n/aunaffected
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.