# CVE-2026-1900: Link Whisper Free < 0.9.1 - Unauthenticated Settings and User Meta Update

> Unauthenticated attackers can modify plugin settings and user metadata via a public REST endpoint in the Link Whisper Free WordPress plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Apr 2026
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-9w5f-xhp2-5782

## What is CVE-2026-1900?

CVE-2026-1900 is a medium-severity missing authorization vulnerability in Unknown Link Whisper Free, published on 7 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Link Whisper Free WordPress plugin before 0.9.1 has a publicly accessible REST endpoint that allows unauthenticated settings updates.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 1 product.


Products: Linkwhisper Link Whisper.

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

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

## Is CVE-2026-1900 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-1900 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-1900 is a medium-severity missing authorization vulnerability in Unknown Link Whisper Free, published on 7 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-1900 exists.

Affected product: Unknown Link Whisper Free. 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-1900/ (Markdown: https://insights.sbomify.com/CVE-2026-1900/index.md)
```

## Sources

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

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