LiveActive security incident?Get immediate response
CVE Record

CVE-2026-32527: WordPress WP Insightly for Contact Form 7, WPForms, Elementor, Formidable and Ninja Forms plugin <= 1.1.5 - Broken Access Control vulnerability

Missing Authorization vulnerability in CRM Perks WP Insightly for Contact Form 7, WPForms, Elementor, Formidable and Ninja Forms cf7-insightly allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP Insightly for Contact Form 7, WPForms, Elementor, Formidable and Ninja Forms: from n/a through <= 1.1.5.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This issue affects a WordPress CRM integration plugin and may let a logged-in low-privilege user access information they should not see. The main business risk is data exposure, not site takeover. Public sources list severity as medium with high confidentiality impact. No cited source confirms active exploitation.

Executive priority

Treat as a moderate-priority WordPress data exposure risk. Prioritize internet-facing sites that use the plugin and allow non-staff logins. Immediate focus should be inventory, exposure reduction, and vendor update monitoring.

Technical view

CVE-2026-32527 is a missing authorization vulnerability (CWE-862) in CRM Perks WP Insightly for Contact Form 7, WPForms, Elementor, Formidable and Ninja Forms, package cf7-insightly, through version 1.1.5. CVSS 3.1 is 6.5: AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N.

Likely exposure

Exposure is limited to WordPress sites with the cf7-insightly plugin installed at version 1.1.5 or earlier. The CVSS vector indicates an attacker needs a low-privilege authenticated account, so sites allowing user registration or many contributor/subscriber accounts may face higher practical risk.

Exploitation context

The public record describes broken access control from missing authorization. It does not provide exploit details, affected endpoints, patch status, or evidence of exploitation in the wild. CISA KEV is not indicated in the provided data.

Researcher notes

Evidence is sparse. The CVE and Patchstack entry identify the affected plugin, version range, CWE, and CVSS vector, but not the vulnerable function, endpoint, proof of concept, or remediation version. Avoid assuming unauthenticated exploitability because CVSS lists PR:L.

Mitigation direction

  • Inventory WordPress sites for the cf7-insightly plugin.
  • Identify installs running version 1.1.5 or earlier.
  • Check CRM Perks, WordPress, or Patchstack guidance for a fixed version.
  • If not business-critical, disable the plugin pending vendor guidance.
  • Limit unnecessary WordPress user accounts and low-privilege access.

Validation and detection

  • Confirm plugin name and package match cf7-insightly.
  • Record installed plugin version on each WordPress site.
  • Check whether public user registration is enabled.
  • Review logs for unusual authenticated access to plugin or CRM-related data.
  • Track vendor advisories for remediation status updates.
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-32527 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
6.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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
CRM PerksWP Insightly for Contact Form 7, WPForms, Elementor, Formidable and Ninja Formscf7-insightly, n/aunaffected
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.