CVE-2025-10567VulnerabilityPublished 5 Nov 2025

The FunnelKit WordPress plugin before 3.12.0.1 does not sanitize user input before echoing it back in some of its

Source GCVE Database

Compare

Authoritative record:CVE-2025-10567· Medium 6.3

Not known to be exploited · CVSS 6.3 Medium.

Data as of 4 Nov 2026, 18:21 UTC

CVSS 3.1 base score

6.3Medium

How severe the flaw is on the 0–10 CVSS scale.

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-8jg3-f28x-33h3

What to do

AI-suggested

Until an official fix is available, users should exercise caution with untrusted input and consider restricting access to the affected AJAX actions or applying web application firewall rules to detect and block reflected XSS payloads.

Description

The FunnelKit WordPress plugin versions prior to 3.12.0.1 contain a reflected cross-site scripting (XSS) vulnerability. This occurs because the plugin does not properly sanitize user input before echoing it back in certain checkout-related AJAX actions. The vulnerability allows attackers to execute reflected XSS attacks against logged-in users.

Impact

Successful exploitation of this vulnerability could allow attackers to execute arbitrary scripts in the context of logged-in users, potentially leading to session hijacking, unauthorized actions, or information disclosure. The impact is limited to confidentiality, integrity, and availability at a low level as per the CVSS vector, and requires user interaction (UI:R).

Summary

CVE-2025-10567 describes a reflected XSS vulnerability in the FunnelKit WordPress plugin before version 3.12.0.1. The flaw arises from insufficient sanitization of user input in some checkout-related AJAX actions, enabling attackers to inject malicious scripts that are reflected back to authenticated users. This vulnerability has a CVSS 3.1 base score of 6.3, indicating a medium severity level.

References

Community reviews

Loading reviews…