# CVE-2026-49083: WordPress LatePoint plugin <= 5.5.1 - Privilege Escalation vulnerability

> A contributor can escalate privileges in the LatePoint WordPress plugin, allowing unauthorized access to higher-level functions.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jun 2026
- **Updated:** 16 Jun 2026
- **Also known as:** GHSA-2prc-85pp-97r9

## What is CVE-2026-49083?

CVE-2026-49083 is a high-severity vulnerability in LatePoint, published on 15 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Contributor Privilege Escalation in LatePoint <= 5.5.1 versions.

Weakness: CWE-266 (Incorrect Privilege Assignment)

## Which versions are affected by CVE-2026-49083?


## How do I fix CVE-2026-49083?

No fix has been published for CVE-2026-49083 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-49083 being exploited?

There is no known exploitation of CVE-2026-49083 in the wild and no public exploit code.

Public exploit code:

- CVE-2026-49083 LatePoint Calendar Booking Plugin Privilege Escalation Exploit (github_poc): https://github.com/izxci/CVE-2026-49083
- https://github.com/87achrafg-stack/CVE-2026-49083 (github_poc): https://github.com/87achrafg-stack/CVE-2026-49083

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-49083 and fix it if it is affected.

What it is: CVE-2026-49083 is a high-severity vulnerability in LatePoint, published on 15 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-49083 in the wild and no public exploit code.

Affected product: LatePoint. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-49083/ (Markdown: https://insights.sbomify.com/CVE-2026-49083/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-49083
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-49083
- OSV: https://osv.dev/vulnerability/CVE-2026-49083

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-49083/
Summaries are generated and may contain mistakes; the official description above is the record.