CVE-2025-31585

Leadfox for WordPress <= 2.1.9 - Cross-Site Request Forgery to Stored Cross-Site Scripting

2025-03-31 00:00

Strategic Overview

Status: Patched in 2.2.0
Affected Plugin: Leadfox for WordPress
Affected Version: <= 2.1.9
CVSS: 6.1Medium
Weakness type: CWE-352 · Cross-Site Request Forgery (CSRF)
CVE: CVE-2025-31585

View all Leadfox for WordPress vulnerabilities

At a glance

CVE-2025-31585 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Leadfox for WordPress WordPress plugin, affecting versions <= 2.1.9. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.2.0; sites on affected versions should update now. Disclosed March 2025, reported by Abdi Pranata.

Vulnerability Overview

The Leadfox for WordPress plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.1.9. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in Leadfox for WordPress <= 2.1.9 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Leadfox for WordPress the fix is 2.2.0: builds <= 2.1.9 are affected, anything from 2.2.0 onward is not.

Remediation

Update to version 2.2.0, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Leadfox for WordPress: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Leadfox for WordPress 2.2.0 closes this, and updating the plugin is the step that ends it.

Firewall
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-31585 https://www.wordfence.com/threat-intel/vulnerabilities/id/0a60ed96-a2c9-45a5-a294-a48c0155683e https://nvd.nist.gov/vuln/detail/CVE-2025-31585

CVSS Vector

6.1

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

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionRequired
ScopeChanged
ConfidentialityLow
IntegrityLow
AvailabilityNone

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/