Foxtool All-in-One: Contact chat button, Custom login, Media optimize images <= 2.5.2 - Cross-Site Request Forgery to Google OAuth Connection
Strategic Overview
- Status
- Patched in 2.5.3
- Affected Version
<= 2.5.2- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2025-13408
At a glance
CVE-2025-13408 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Foxtool All-in-One WordPress plugin, affecting versions <= 2.5.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.5.3; sites on affected versions should update now. Disclosed December 2025, reported by D01EXPLOIT OFFICIAL.
Vulnerability Overview
The Foxtool All-in-One: Contact chat button, Custom login, Media optimize images plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.5.2. This is due to missing or incorrect nonce validation on the foxtool_login_google() function. This makes it possible for unauthenticated attackers to establish an OAuth Connection 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)
Foxtool All-in-One <= 2.5.2 carries this weakness at foxtool_login_google(), and reaching it 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 Foxtool All-in-One the fix is 2.5.3: builds <= 2.5.2 are affected, anything from 2.5.3 onward is not.
Remediation
Update to version 2.5.3, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Foxtool All-in-One: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Foxtool All-in-One 2.5.3 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C