CVE-2026-49083
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 · uneditedContributor Privilege Escalation in LatePoint <= 5.5.1 versions.
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 · moderate confidenceThis is a privilege escalation vulnerability in the LatePoint WordPress appointment booking plugin (versions 5.5.1 and below). The flaw allows users with the contributor role to elevate their privileges beyond what that role should permit, likely by exploiting insufficient authorization checks in the plugin's functionality.
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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
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 if LatePoint plugin is installedIn WordPress admin, go to Plugins > Installed Plugins. Look for 'LatePoint' in the list of active plugins.Affected if LatePoint is installed and active on the WordPress site
-
Check the installed LatePoint versionIn WordPress admin, go to Plugins > Installed Plugins. Click on the LatePoint plugin to view its details, or check the plugin header comment in /wp-content/plugins/latepoint/ folder via file manager or FTP.Affected if The displayed version is 5.5.1 or any version below 5.5.1 (e.g., 5.5.0, 5.4.x, etc.)
-
Verify if contributor role accounts existIn WordPress admin, go to Users > All Users. Look for any users assigned the 'Contributor' role in the Role column.Affected if At least one user with contributor role exists on the site
-
Audit user accounts for privilege escalationIn WordPress admin, go to Users > All Users. Review each account and check if any contributor-level accounts now have administrator or higher-level access, or if new admin accounts were created that you do not recognize.Affected if Any contributor account shows elevated privileges or unexpected administrator accounts are present
The environment is affected if LatePoint is installed with version 5.5.1 or below and contributor role users exist on the site.
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.
dbcve · scopedUpdate LatePoint to the latest version immediately. Review user accounts with contributor-level access and audit for any unauthorized changes or privilege escalation that may have already occurred.
LatePoint 5.5.2 or later
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find LatePoint in the plugin list
- Check if an update is available (if not, check the plugin vendor website directly for the latest version)
- If update available, click 'Update Now' and wait for it to complete
- Verify the update was successful by checking the plugins list shows version 5.5.2 or later
- Test that contributor-level users can no longer perform administrative actions
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-49083 — 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-49083 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