LiveActive security incident?Get immediate response
CVE Record

CVE-2026-32533: WordPress LatePoint plugin <= 5.2.6 - Insecure Direct Object References (IDOR) vulnerability

Authorization Bypass Through User-Controlled Key vulnerability in LatePoint LatePoint latepoint allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects LatePoint: from n/a through <= 5.2.6.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-32533 affects the WordPress LatePoint plugin through version 5.2.6. It is an authorization weakness where a user-controlled identifier may let someone access or modify objects they should not control. The published score is medium, but exposure depends on whether LatePoint is installed and reachable on public WordPress sites.

Executive priority

Treat this as a moderate-priority WordPress plugin issue. It is not confirmed exploited in the provided sources, but it may be remotely reachable without login. Prioritize identifying exposed LatePoint deployments and applying vendor-supported remediation when available.

Technical view

The issue is an Insecure Direct Object Reference / authorization bypass mapped to CWE-639 in LatePoint <= 5.2.6. CVSS 3.1 is 6.5: network exploitable, low complexity, no privileges, no user interaction, with low integrity and availability impact and no confidentiality impact reported.

Likely exposure

Organizations using the LatePoint WordPress plugin on internet-facing sites are the primary concern. Sites not running LatePoint, or running versions outside the affected range, are not indicated as affected by the provided sources.

Exploitation context

The CVE data does not indicate CISA KEV listing, and the provided sources do not state active exploitation. The CVSS vector indicates remote unauthenticated exploitability, but no exploit details should be assumed from the available evidence.

Researcher notes

Evidence is limited to the CVE record and Patchstack entry. The affected range is stated as LatePoint through <= 5.2.6. No specific vulnerable endpoint, proof of concept, patched version, or active exploitation evidence is provided in the source bundle.

Mitigation direction

  • Inventory WordPress sites for the LatePoint plugin.
  • Identify any LatePoint installations at version 5.2.6 or earlier.
  • Check LatePoint and Patchstack guidance for fixed versions or vendor mitigations.
  • Prioritize remediation for public sites accepting bookings or customer interactions.
  • Restrict unnecessary public access to affected functionality where operationally feasible.

Validation and detection

  • Confirm whether each WordPress site has LatePoint installed.
  • Record the installed LatePoint version for each site.
  • Compare versions against the affected range: through 5.2.6.
  • Review access-control logs for unusual object changes or booking modifications.
  • Monitor the CVE and vendor references for updated remediation details.
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 · low confidence lookup

CWE-639: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-32533 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:N/UI:N/S:U/C:N/I:L/A:L

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:N/UI:N/S:U/C:N/I:L/A:L3.92.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2026-32533Attack 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:L

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
LatePointLatePointlatepoint, n/aunaffected
Weakness

CWE details

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

CWE-639 · source CWE mapping

Authorization Bypass Through User-Controlled Key

Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.