Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-13906: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in ysh WP Flot

0
Medium
VulnerabilityCVE-2025-13906cvecve-2025-13906cwe-79
Published: Fri Dec 12 2025 (12/12/2025, 03:20:54 UTC)
Source: CVE Database V5
Vendor/Project: ysh
Product: WP Flot

Description

The WP Flot plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'linechart' shortcode in all versions up to, and including, 0.2.2 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.

AI-Powered Analysis

AILast updated: 12/19/2025, 05:08:02 UTC

Technical Analysis

CVE-2025-13906 identifies a stored cross-site scripting vulnerability in the WP Flot plugin for WordPress, specifically within the 'linechart' shortcode functionality. This vulnerability stems from improper neutralization of input during web page generation (CWE-79), where user-supplied attributes are not adequately sanitized or escaped before rendering. As a result, authenticated users with contributor-level access or higher can inject arbitrary JavaScript code into pages. When other users access these pages, the malicious scripts execute in their browsers, potentially leading to session hijacking, privilege escalation, or unauthorized actions within the WordPress environment. The vulnerability affects all versions up to and including 0.2.2 of the WP Flot plugin. The CVSS 3.1 base score is 6.4, reflecting a medium severity with network attack vector, low attack complexity, privileges required (contributor level), no user interaction, and a scope change due to impact on other users. Although no active exploits have been reported, the vulnerability's presence in a popular CMS plugin makes it a notable risk. The lack of official patches at the time of publication necessitates immediate mitigation efforts by administrators.

Potential Impact

For European organizations, this vulnerability can lead to unauthorized script execution within their WordPress sites, compromising user sessions, leaking sensitive information, or enabling further attacks such as privilege escalation or defacement. Given WordPress's widespread use across Europe, especially in small and medium enterprises, government portals, and e-commerce platforms, exploitation could disrupt business operations and damage reputations. The requirement for contributor-level access limits exploitation to insiders or compromised accounts, but social engineering or credential theft could facilitate this. The cross-site scripting nature primarily threatens confidentiality and integrity, with no direct availability impact. However, successful exploitation could serve as a foothold for more severe attacks. Organizations handling personal data under GDPR must consider the regulatory implications of such breaches. The medium severity score suggests a moderate but actionable risk that should not be ignored.

Mitigation Recommendations

1. Immediately restrict contributor-level permissions to trusted users only and review existing user roles for potential abuse. 2. Monitor and audit the use of the 'linechart' shortcode in site content to detect suspicious or unauthorized injections. 3. Implement web application firewalls (WAF) with rules to detect and block malicious script payloads targeting WordPress shortcodes. 4. Apply manual input sanitization and output escaping in custom code or consider disabling the WP Flot plugin until an official patch is released. 5. Educate content contributors about the risks of injecting untrusted content and enforce strict content validation policies. 6. Regularly update WordPress core and plugins, and subscribe to security advisories for timely patch application once available. 7. Employ Content Security Policy (CSP) headers to limit the execution of unauthorized scripts within the site context. 8. Conduct periodic security assessments focusing on user-generated content vulnerabilities.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-12-02T16:36:09.590Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 693b9185650da22753edbce3

Added to database: 12/12/2025, 3:52:37 AM

Last enriched: 12/19/2025, 5:08:02 AM

Last updated: 2/7/2026, 1:36:07 AM

Views: 43

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats