LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1611: Wikiloops Track Player <= 1.0.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode

The Wikiloops Track Player plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's `wikiloops` shortcode in all versions up to, and including, 1.0.1 due to insufficient input sanitization and output escaping on user supplied attributes. 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-1611 affects the Wikiloops Track Player WordPress plugin through version 1.0.1. A logged-in user with Contributor-level access or higher can save malicious script content through the plugin shortcode. That script can run for visitors who view the affected page, creating risk to site users and administrative sessions.

Executive priority

Treat as a routine but timely WordPress plugin risk. Prioritize sites with many contributors, external content authors, or sensitive logged-in users. No active exploitation is cited in the provided sources.

Technical view

The issue is stored cross-site scripting in the `wikiloops` shortcode caused by insufficient sanitization and output escaping of shortcode attributes. It is classified as CWE-79 with CVSS 3.1 score 6.4. The attack requires authenticated low-privilege access and can affect confidentiality and integrity, with scope changed.

Likely exposure

Exposure is limited to WordPress sites running Wikiloops Track Player up to and including 1.0.1, especially where Contributor or higher accounts are available to less-trusted users.

Exploitation context

The provided sources do not indicate known active exploitation or CISA KEV listing. Exploitation requires authenticated Contributor-level or higher access and a page using the vulnerable shortcode behavior.

Researcher notes

Evidence names versions up to 1.0.1 and identifies the shortcode source location. No fixed version, exploit activity, or vendor mitigation is provided in the source bundle, so remediation should be verified against current plugin guidance.

Mitigation direction

  • Check vendor and WordPress plugin guidance for an updated fixed release.
  • Update the plugin if a fixed version is available.
  • Disable or remove the plugin if it is not business-critical.
  • Limit Contributor and higher roles to trusted users only.
  • Review published content using the Wikiloops shortcode.

Validation and detection

  • Inventory WordPress sites for Wikiloops Track Player installations.
  • Confirm whether installed versions are 1.0.1 or earlier.
  • Review which users have Contributor, Author, Editor, or Administrator roles.
  • Inspect pages and posts using the `wikiloops` shortcode for unexpected attributes.
  • Check security logs for suspicious edits by low-privilege accounts.
Prepared
Confidence
medium
Sources
4

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-1611 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
3Source 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-1611Attack 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
jmrukkersWikiloops Track Player0unaffected
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.