CVE-2025-31383: FrescoChat Live Chat CSRF Vulnerability

CVE-2025-31383 Overview

CVE-2025-31383 is a Cross-Site Request Forgery (CSRF) vulnerability in the sodena FrescoChat Live Chat WordPress plugin (flexytalk-widget) that enables Stored Cross-Site Scripting (XSS). The flaw affects all versions of FrescoChat Live Chat up to and including 3.2.6. An attacker can craft a malicious request that, when triggered by an authenticated administrator, persists attacker-controlled JavaScript into the plugin's stored settings. The injected payload then executes in the browser of every user who renders the affected page. The weakness is categorized under CWE-352: Cross-Site Request Forgery.

Critical Impact

A single click on an attacker-controlled link by an authenticated WordPress administrator can result in persistent JavaScript injection across the affected site, leading to session theft, account takeover, or further compromise of site visitors.

Affected Products

• sodena FrescoChat Live Chat WordPress plugin (flexytalk-widget)
• All versions from n/a through <= 3.2.6
• WordPress sites with the plugin installed and active

Discovery Timeline

• 2025-04-09 - CVE-2025-31383 published to NVD
• 2026-04-23 - Last updated in NVD database

Technical Details for CVE-2025-31383

Vulnerability Analysis

The vulnerability chains two distinct weaknesses into a single exploitable issue. First, a state-changing administrative endpoint in the flexytalk-widget plugin fails to validate an anti-CSRF token (such as a WordPress nonce) before processing requests. Second, user-supplied input accepted by that endpoint is stored without proper sanitization or output encoding, producing a Stored XSS condition.

When an authenticated administrator visits an attacker-controlled page, the browser silently submits a forged request to the WordPress site. The request writes attacker-supplied JavaScript into the plugin's stored configuration. The payload then executes in the context of any user who loads a page rendering that configuration.

Exploitation requires user interaction, which limits drive-by abuse but aligns with typical phishing-driven CSRF scenarios. The EPSS score for this CVE is 0.08%.

Root Cause

The root cause is missing CSRF protection on a privileged plugin endpoint combined with insufficient sanitization of stored input. WordPress provides wp_verify_nonce() and check_admin_referer() helpers to defend against CSRF, and wp_kses() or esc_attr()/esc_html() for output encoding. The vulnerable code paths in flexytalk-widget versions through 3.2.6 invoke neither category of control on the affected handler.

Attack Vector

The attack is delivered over the network and requires that a logged-in WordPress administrator load an attacker-controlled page or click a crafted link. The forged request modifies plugin settings to embed a JavaScript payload. Subsequent visitors, including unauthenticated site users, execute the script in their browser session against the trusted site origin.

No verified exploit code is publicly available. Refer to the Patchstack Vulnerability Report for additional technical context.

Detection Methods for CVE-2025-31383

Indicators of Compromise

• Unexpected <script> tags, onerror= attributes, or external JavaScript references stored in FrescoChat plugin options within the wp_options table.
• Outbound requests from site visitors to unknown third-party domains originating from pages that render the chat widget.
• Administrator audit logs showing plugin settings updates that do not correlate with legitimate admin activity.

Detection Strategies

• Inspect plugin configuration fields under the flexytalk-widget namespace for HTML or JavaScript content that should contain only plain text or numeric values.
• Monitor WordPress access logs for POST requests to plugin admin endpoints lacking a valid Referer header from the same origin.
• Deploy a Web Application Firewall (WAF) rule that flags state-changing requests to wp-admin endpoints originating from cross-origin contexts.

Monitoring Recommendations

• Enable WordPress activity logging to capture plugin option changes with user, IP, and timestamp attribution.
• Implement Content Security Policy (CSP) headers and alert on CSP violation reports indicating inline script execution from the chat widget.
• Continuously scan installed plugins against vulnerability databases such as Patchstack and the WordPress Plugin Directory.

How to Mitigate CVE-2025-31383

Immediate Actions Required

• Identify all WordPress instances running FrescoChat Live Chat (flexytalk-widget) version 3.2.6 or earlier.
• Deactivate the plugin until a patched version is confirmed available and installed.
• Audit plugin settings and the wp_options table for any injected script content and remove it.
• Rotate WordPress administrator credentials and invalidate active sessions if compromise is suspected.

Patch Information

At the time of publication, the Patchstack Vulnerability Report lists all versions through <= 3.2.6 as affected. Administrators should monitor the vendor's plugin page for an update beyond 3.2.6 that adds nonce verification and output encoding, then apply it immediately.

Workarounds

• Remove or deactivate the flexytalk-widget plugin if a patched release is unavailable.
• Restrict access to /wp-admin/ using IP allowlists, VPN, or HTTP authentication to reduce CSRF exposure.
• Enforce a strict Content Security Policy that disallows inline scripts and restricts script sources to trusted origins.
• Require administrators to use browsers with separate profiles for WordPress administration to limit ambient session abuse.