CVE-2026-25441
Missing Authorization in LeadConnector ≤ 3.0.21 Enables Unauthorized Access
Publication date: 2026-02-19
Last updated on: 2026-04-23
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| leadconnector | leadconnector | to 3.0.21 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-862 | The product does not perform an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability impact me? :
Because the vulnerability allows unauthenticated users to perform privileged actions, it can lead to unauthorized access or manipulation of the system.
However, the CVSS severity score is 5.3, indicating a low priority and low severity impact, and it is considered unlikely to be exploited in a significant manner.
Despite the low severity, the vulnerability requires no privileges to exploit, so timely patching is important to prevent potential misuse.
Can you explain this vulnerability to me?
CVE-2026-25441 is a Broken Access Control vulnerability in the WordPress LeadConnector Plugin versions up to and including 3.0.21.
This vulnerability arises from missing authorization, authentication, or nonce token checks within certain functions, allowing unauthenticated users to perform actions that should be restricted to higher-privileged users.
It falls under the OWASP Top 10 category A1: Broken Access Control.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'This vulnerability arises from missing authorization and authentication checks in the LeadConnector WordPress plugin, allowing unauthenticated users to perform privileged actions.'}, {'type': 'paragraph', 'content': 'Detection typically involves checking the plugin version installed on your WordPress site to see if it is version 3.0.21 or earlier, as these versions are vulnerable.'}, {'type': 'paragraph', 'content': 'There are no specific network or system commands provided to detect exploitation attempts or presence of this vulnerability.'}, {'type': 'paragraph', 'content': 'A practical approach is to verify the plugin version via WordPress admin dashboard or by running commands to check the plugin version, for example:'}, {'type': 'list_item', 'content': 'Using WP-CLI: wp plugin list | grep leadconnector'}, {'type': 'list_item', 'content': "Manually checking the plugin version in the plugin's main PHP file or via the WordPress admin interface."}] [1]
What immediate steps should I take to mitigate this vulnerability?
The primary and immediate mitigation step is to update the LeadConnector plugin to version 3.0.22 or later, where this vulnerability has been patched.
If updating immediately is not possible, consider disabling the plugin temporarily to prevent exploitation.
Additionally, ensure that your WordPress installation and other plugins are kept up to date and monitor for any unusual activity.
Using automated update tools such as Patchstack can help rapidly protect vulnerable plugins.