CVE-2026-32533
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAuthorization 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · low confidenceAn Authorization Bypass Through User-Controlled Key vulnerability (IDOR-style) in LatePoint plugin <=5.2.6 allows authenticated users to access or modify resources belonging to other users by manipulating object identifiers in requests, exploiting incorrectly configured access control security levels.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify LatePoint plugin installationLocate the LatePoint plugin files in the wp-content/plugins directory of the WordPress installation and check the main plugin file header for the version numberAffected if LatePoint plugin is installed and the version is 5.2.6 or lower
-
Verify authenticated user access existsConfirm that the WordPress site has user registration or membership functionality enabled, allowing non-admin users to authenticate to the LatePoint systemAffected if The site allows authenticated user accounts beyond administrators
-
Check for object reference parameters in LatePoint requestsReview API endpoints or AJAX handlers used by LatePoint for parameters that reference user-owned objects (such as booking IDs, customer IDs, or resource identifiers)Affected if Requests contain direct object identifiers that can be modified by the requesting user
-
Test ownership validation on sensitive endpointsSubmit requests to LatePoint endpoints (such as booking retrieval, modification, or deletion) using valid authentication but with object IDs belonging to a different user accountAffected if Requests succeed when accessing or modifying objects owned by other users without proper authorization verification
A user is affected if LatePoint plugin version 5.2.6 or lower is installed AND the site has authenticated user accounts AND direct object references in requests are not validated for ownership before allowing access or modification.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper authorization checks validating that the requesting user has permission to access the requested object; use indirect references and enforce ownership validation on all sensitive operations.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32533 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-32533 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data