LiveActive security incident?Get immediate response
CVE Record

CVE-2026-25441: WordPress LeadConnector plugin <= 3.0.21 - Broken Access Control vulnerability

Missing Authorization vulnerability in varunvairavanlc LeadConnector leadconnector allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects LeadConnector: from n/a through <= 3.0.21.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-25441 affects the WordPress LeadConnector plugin up to version 3.0.21. It is a broken access control issue, meaning some action may be allowed without proper permission checks. The published impact is limited to integrity, not data disclosure or service outage. Treat this as a priority for WordPress sites using this plugin, but current sources do not show active exploitation.

Executive priority

Moderate priority. This is remotely reachable and requires no login, but published impact is limited to unauthorized integrity changes. Address during the next WordPress security maintenance cycle, sooner for high-value or internet-facing sites using the plugin.

Technical view

The issue is CWE-862 Missing Authorization in varunvairavanlc LeadConnector for WordPress, affecting versions through 3.0.21. CVSS 3.1 is 5.3: network reachable, low complexity, no privileges, no user interaction, unchanged scope, low integrity impact only. Public details do not identify the specific endpoint, action, or fixed version.

Likely exposure

Exposure is limited to WordPress installations with the LeadConnector plugin installed at version 3.0.21 or earlier. Internet-facing WordPress sites are more reachable, but the source data does not confirm which plugin functionality is affected.

Exploitation context

The CVE record and Patchstack entry describe missing authorization with low integrity impact. The issue is not listed as CISA KEV in the provided bundle, and no cited source states active exploitation or public weaponization.

Researcher notes

Source detail is sparse. The description supports missing authorization through version 3.0.21, but the affected-product metadata in the bundle is limited and does not name a fixed version. Avoid assuming exploitability beyond the CVSS and Patchstack/CVE statements.

Mitigation direction

  • Inventory WordPress sites for the LeadConnector plugin and installed version.
  • Prioritize sites running LeadConnector version 3.0.21 or earlier.
  • Check Patchstack, WordPress plugin, or vendor guidance for a fixed release or workaround.
  • If not business-critical, disable the plugin until remediation guidance is available.
  • Apply least-privilege controls and monitor WordPress administrative activity.

Validation and detection

  • Confirm whether LeadConnector is installed on each WordPress site.
  • Record the plugin version and compare it to 3.0.21 or earlier.
  • Review vendor or Patchstack advisories for updated affected and fixed-version details.
  • Check logs for unexpected configuration or content changes related to the plugin.
  • Verify remediation by confirming the plugin is updated, disabled, or otherwise addressed.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-25441 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2026-25441Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
varunvairavanlcLeadConnectorleadconnector, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.