# CVE-2026-119682: Improper Access Control in Multi-Factor Authentication (MFA) Functionality in ManageEngine SharePoint Manager Plus


- **Severity:** High 7.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 30 Oct 2026
- **Updated:** 6 Nov 2026
- **Also known as:** GHSA-rfrw-7qrh-fh28

## What is CVE-2026-119682?

CVE-2026-119682 is a high-severity vulnerability in ManageEngine SharePoint Manager Plus, published on 30 Oct 2026. 

### Official description

An improper access control vulnerability exists in the multi-factor authentication (MFA) functionality of ManageEngine SharePoint Manager Plus (SPMP). A low-privileged authenticated user can bypass authorization checks to read and modify MFA configuration settings, enable or disable MFA for the application, enumerate MFA-enrolled users, and delete MFA-enrolled accounts. Successful exploitation could allow an attacker to weaken authentication protections or cause a denial of service by configuring invalid MFA settings, potentially locking legitimate users out of the application. This vulnerability was fixed in build 4507. The reproduction explicitly uses build 4506.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-119682 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-119682 is a high-severity vulnerability in ManageEngine SharePoint Manager Plus, published on 30 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-119682 in the wild and no public exploit code.

Affected product: ManageEngine SharePoint Manager Plus. 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-119682/ (Markdown: https://insights.sbomify.com/CVE-2026-119682/index.md)
```

## Sources

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

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