Skip to main content
Vulnerability Database/CVE-2025-12663

CVE-2025-12663: Jeba Cute Forkit WordPress Plugin XSS

CVE-2025-12663 is a stored cross-site scripting flaw in the Jeba Cute Forkit WordPress plugin that allows authenticated attackers to inject malicious scripts. This article covers technical details, affected versions, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2025-12663 Overview

CVE-2025-12663 is a stored cross-site scripting (XSS) vulnerability in the Jeba Cute Forkit plugin for WordPress. The flaw affects all versions up to and including 1.0. The vulnerability exists in the text parameter of the jeba_forkit shortcode due to insufficient input sanitization and output escaping on user-supplied attributes. Authenticated attackers with contributor-level access or higher can inject arbitrary JavaScript into pages. Injected scripts execute in the browser of any user who accesses the affected page. The issue is tracked under CWE-79 and was published to the National Vulnerability Database on November 11, 2025.

Critical Impact

Authenticated contributors can persist arbitrary JavaScript into WordPress pages, enabling session theft, administrative account takeover, and site-wide redirection attacks.

Affected Products

  • Jeba Cute Forkit plugin for WordPress — all versions through 1.0
  • WordPress sites allowing contributor-level or higher accounts
  • Any WordPress installation using the jeba_forkit shortcode

Discovery Timeline

  • 2025-11-11 - CVE-2025-12663 published to NVD
  • 2026-06-17 - Last updated in NVD database

Technical Details for CVE-2025-12663

Vulnerability Analysis

The Jeba Cute Forkit plugin registers a shortcode named jeba_forkit that accepts user-controlled attributes. The text attribute is rendered into page output without proper sanitization or escaping. When a contributor publishes a post containing the shortcode with a malicious text value, the stored payload executes in every visitor's browser.

Stored XSS carries greater weight than reflected XSS because the payload persists in the database. Any authenticated session that renders the affected page becomes a potential target, including administrator sessions. Attackers can use the primitive to hijack sessions, exfiltrate nonces, modify page content, or chain into privilege escalation by forcing an administrator browser to perform authenticated actions.

Root Cause

The vulnerable code path in jeba-forkit-index.php renders the shortcode text attribute directly into HTML output. WordPress provides esc_html(), esc_attr(), and wp_kses() helpers for safe rendering, but the plugin does not apply them to this attribute. See the WordPress Plugin Code Review for the vulnerable source line.

Attack Vector

Exploitation requires an authenticated account with contributor privileges or higher. The attacker creates or edits a post containing the jeba_forkit shortcode with a text attribute carrying a JavaScript payload, for example an inline event handler or <script> tag embedded in attribute context. Once the post is viewed by any user, including administrators, the script executes under the site's origin. Additional technical analysis is available in the Wordfence Vulnerability Report.

No verified public exploit code is available at the time of writing. The vulnerability can be reproduced by placing a crafted shortcode in post content and loading the resulting page.

Detection Methods for CVE-2025-12663

Indicators of Compromise

  • Post or page content containing the jeba_forkit shortcode with suspicious attribute values such as <script>, onerror=, onload=, or javascript: strings
  • Unexpected outbound requests from visitor browsers to attacker-controlled domains after loading pages that render the shortcode
  • New or modified WordPress administrator accounts created shortly after a contributor publishes content using the plugin
  • Session cookies or REST API nonces observed in web server logs being forwarded to third-party endpoints

Detection Strategies

  • Query the wp_posts table for rows where post_content matches the pattern [jeba_forkit and inspect the text attribute values for HTML or JavaScript constructs
  • Deploy web application firewall rules that inspect POST bodies to wp-admin/post.php for shortcode attributes containing script syntax
  • Enable Content Security Policy reporting to surface inline script execution originating from stored content

Monitoring Recommendations

  • Audit contributor-level and author-level accounts for unexpected activity, focusing on recent post creations and revisions
  • Monitor WordPress audit logs for shortcode-containing posts transitioning from draft to published status
  • Alert on any modification to plugin files under wp-content/plugins/jeba-cute-forkit/

How to Mitigate CVE-2025-12663

Immediate Actions Required

  • Deactivate and remove the Jeba Cute Forkit plugin from affected WordPress installations until a patched release is available
  • Audit all published and draft content for existing jeba_forkit shortcode usage and remove suspicious attribute values
  • Rotate administrator passwords and invalidate active sessions if the plugin has been active with contributor accounts present
  • Review contributor and author account rosters and remove unused or untrusted accounts

Patch Information

No patched version is listed in the NVD advisory. All versions up to and including 1.0 remain vulnerable. Site operators should monitor the plugin page on WordPress.org for a security release and apply updates when available.

Workarounds

  • Remove the plugin entirely if the shortcode is not business-critical
  • Restrict the user roles permitted to use the Shortcake or shortcode interfaces using a role-management plugin
  • Enforce a strict Content Security Policy that disallows inline scripts, reducing the impact of stored XSS payloads
  • Place the site behind a web application firewall with rules blocking script syntax in shortcode attributes
bash
# Remove the vulnerable plugin via WP-CLI
wp plugin deactivate jeba-cute-forkit
wp plugin delete jeba-cute-forkit

# Search existing content for the vulnerable shortcode
wp db query "SELECT ID, post_title FROM wp_posts WHERE post_content LIKE '%[jeba_forkit%';"

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.