CVE-2025-14162
CSRF in BMLT WordPress Plugin Allows Unauthorized Settings Changes
Publication date: 2025-12-12
Last updated on: 2025-12-12
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wordpres | plugin | bmlt |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-352 | The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor. |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability is a Cross-Site Request Forgery (CSRF) issue in the BMLT WordPress Plugin versions up to 3.11.4, caused by missing nonce validation on specific plugin actions. Detection typically involves monitoring for unauthorized or forged requests targeting the 'BMLTPlugin_create_option' and 'BMLTPlugin_delete_option' actions. Since the vulnerability requires tricking an administrator into clicking a malicious link, network detection could include inspecting HTTP requests for unexpected POST or GET requests to these plugin endpoints without valid nonce tokens. However, no specific detection commands or tools are provided in the available resources.
Can you explain this vulnerability to me?
This vulnerability is a Cross-Site Request Forgery (CSRF) in the BMLT WordPress Plugin up to version 3.11.4. It occurs because the plugin lacks nonce validation on certain actions ('BMLTPlugin_create_option' and 'BMLTPlugin_delete_option'), allowing an attacker to trick a site administrator into performing unintended actions, such as creating new plugin settings via a forged request.
How can this vulnerability impact me? :
An attacker can exploit this vulnerability to create new plugin settings without authorization by tricking an administrator into clicking a malicious link. This can lead to unauthorized changes in the plugin configuration, potentially compromising the site's integrity or security.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update the BMLT WordPress Plugin to a version later than 3.11.4 where the nonce validation issue is fixed. Additionally, avoid clicking on suspicious links and ensure that only trusted administrators have access to the WordPress backend to reduce the risk of CSRF attacks.