# CVE-2026-114743: InstaWP Connect < 0.1.4.2 - Authenticated Plugin Settings Update via instawp_update_settings


- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 25 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-587v-fw9w-xc4m

## What is CVE-2026-114743?

CVE-2026-114743 is a low-severity vulnerability in Unknown InstaWP Connect, published on 25 Oct 2026. 

### Official description

The InstaWP Connect  WordPress plugin before 0.1.4.2 does not perform a capability check on its InstaWP Connect  WordPress plugin before 0.1.4.2-settings update action, verifying only a nonce, allowing an authenticated user holding a low-privileged role that an administrator has granted access to the InstaWP Connect  WordPress plugin before 0.1.4.2's sync feature to overwrite the InstaWP Connect  WordPress plugin before 0.1.4.2's settings, including the setting controlling which roles may access that feature. The role grant is not enabled by default.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-114743 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114743 is a low-severity vulnerability in Unknown InstaWP Connect, published on 25 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114743 in the wild and no public exploit code.

Affected product: Unknown InstaWP Connect. 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-114743/ (Markdown: https://insights.sbomify.com/CVE-2026-114743/index.md)
```

## Sources

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

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