BMLT WordPress Plugin <= 3.11.4 - Cross-Site Request Forgery to Settings Creation and Deletion
Strategic Overview
- Status
- Patched in 3.11.5
- Affected Plugin
- BMLT WordPress Satellite
- Affected Version
<= 3.11.4- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2025-14162
At a glance
CVE-2025-14162 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the BMLT WordPress Satellite WordPress plugin, affecting versions <= 3.11.4. 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 3.11.5; sites on affected versions should update now. Disclosed December 2025, reported by Muhammad Nur Ibnu Hubab.
Vulnerability Overview
The BMLT WordPress Plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.11.4. This is due to missing nonce validation on the 'BMLTPlugin_create_option' and 'BMLTPlugin_delete_option ' action. This makes it possible for unauthenticated attackers to create new plugin settings 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)
BMLT WordPress Satellite <= 3.11.4 carries this weakness at BMLTPlugin_create_option, 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 BMLT WordPress Satellite the fix is 3.11.5: builds <= 3.11.4 are affected, anything from 3.11.5 onward is not.
Remediation
Update to version 3.11.5, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to BMLT WordPress Satellite: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: BMLT WordPress Satellite 3.11.5 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